Wifi adapter is connected to the network but as a separate device and does not distribute the Internet to the computer?

Question

linux

Hello.
The question is a little unclear and there is a hint of lamerism, but I just have no idea how to formulate it differently.
I decided to make myself a home server out of an old pitch. I connected via ethernet. Installed packages, configured settings. When I finished and it was time to switch from ethernet to wifi (yes, it's just far from the ethernet cable, and the connection speed is not so important for me), I plugged in the adapter (TP-Link TL WN823N). I downloaded firewood (RTL8192EU), compiled it, loaded it. It looks like the process has begun. Connected to my home network via nmcli. It seems that everything even worked (so the nmcli dev status exhaust says). But the network is not working. Checked with nmap. Everything seems to be working. I checked with the Fing application (yes it is for a smartphone, and yes it can determine what kind of device is sitting under the current ip (pc , router , etc)). It shows me that it is not the PC itself that is connected, but the wifi adapter as a separate device. At the same time, the PC has a static ip, but the adapter is connected under a completely different one. It's like it's a separate device. Maybe someone faced such a problem (it just came as a surprise to me) and can help me
PS I tried various drivers (rtl8192eu and rtl8192cu). In fact, it's one and the same. No result (and even if the problem was in the drivers, the adapter would simply not be determined)
Thanks in advance for your answer

Answer 1

Sorry, the description is a little unclear: how is your routing configured?
what does ip route say? gw (default) where does it look?
I'm wildly sorry, but a PC cannot have an ip. ip is assigned to the INTERFACE (network card if it's rude), and yes 127.0.0.1 is also an interface, it's just virtual :)
If you have a wired and wireless network in your computer at the same time, then they should both have ip assigned from different (!!!) ranges, so that the system does not think "where should I send the packet", but simply looked into the routing table and threw the packet into the interface that matches the range.
Those. if you have already assigned a static ip on a wired network, and you are trying to assign a wireless ip from the same range, then nothing will take off.
look at what the following commands will answer:
ip address
ip route
and immediately everything will become clear and understandable.
If not - write :)