rtl8187 works with all other wifi networks except my home's one.

mamograg17 · 2022-06-15 08:26:53

Hello,
I have an rtl8187, it is a usb wifi card, the system reads it and it shows wifi networks, when i connect to my wifi, network manager keeps saying that this wifi has no internet access and when i try to load some web page it is not working,
so i tried to connect to another wifi and it works well all the applications work, i am sure that my wifi has internet access cause it works well in other devices,

this is what i get when i ping 8.8.8.8:

╰─ ping 8.8.8.8                                                                                                                                                            ─╯
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.104 icmp_seq=15 Destination Host Unreachable
From 192.168.1.104 icmp_seq=16 Destination Host Unreachable
From 192.168.1.104 icmp_seq=17 Destination Host Unreachable
From 192.168.1.104 icmp_seq=18 Destination Host Unreachable
From 192.168.1.104 icmp_seq=19 Destination Host Unreachable
From 192.168.1.104 icmp_seq=20 Destination Host Unreachable
From 192.168.1.104 icmp_seq=21 Destination Host Unreachable
From 192.168.1.104 icmp_seq=22 Destination Host Unreachable
From 192.168.1.104 icmp_seq=23 Destination Host Unreachable
^C
--- 8.8.8.8 ping statistics ---
25 packets transmitted, 0 received, +9 errors, 100% packet loss, time 24612ms
pipe 3

please how can i solve this problem?

Last edited by mamograg17 (2022-06-15 09:12:40)

seth · 2022-06-15 10:48:15

this is what i get when i ping 8.8.8.8

That's pretty useless, please post a complete system journal ("sudo journalctl -b > /tmp/system_journal..txt") after this happened.
Also try to

ping _gateway

Anecdotally, some APs don't like https://wiki.archlinux.org/title/Networ … domization so disable that and maybe this is a WPA3 situation, https://wiki.archlinux.org/title/Wpa_su … ess_points and the following paragraph.

mamograg17 · 2022-06-15 11:39:54

seth wrote:

please post a complete system journal ("sudo journalctl -b > /tmp/system_journal..txt") after this happened.

here are the logs:
https://pastebin.com/Wd63SxGP

seth wrote:

Also try to
ping _gateway

this is what i get:

╰─ ping _gateway                                                                                                                             
PING _gateway (192.168.1.1) 56(84) bytes of data.
From mamograg (192.168.1.104) icmp_seq=2 Destination Host Unreachable
From mamograg (192.168.1.104) icmp_seq=3 Destination Host Unreachable
From mamograg (192.168.1.104) icmp_seq=4 Destination Host Unreachable
From mamograg (192.168.1.104) icmp_seq=5 Destination Host Unreachable
From mamograg (192.168.1.104) icmp_seq=6 Destination Host Unreachable
^C
--- _gateway ping statistics ---
8 packets transmitted, 0 received, +5 errors, 100% packet loss, time 7192ms
pipe 4

and also i tried the randomization solution, but nothing the changes stop the network manager at boot.

Last edited by mamograg17 (2022-06-15 11:41:31)

seth · 2022-06-15 11:55:11

Jun 15 11:26:33 mamograg wpa_supplicant[425]: wlp0s20f0u3: CTRL-EVENT-CONNECTED - Connection to 98:48:27:90:5c:3e completed [id=0 id_str=]
Jun 15 11:26:33 mamograg kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f0u3: link becomes ready
Jun 15 11:26:33 mamograg NetworkManager[384]: <info>  [1655292393.7872] device (wlp0s20f0u3): supplicant interface state: 4way_handshake -> completed
Jun 15 11:26:33 mamograg NetworkManager[384]: <info>  [1655292393.7872] device (wlp0s20f0u3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "TP-LINK_905C3E"
Jun 15 11:26:33 mamograg NetworkManager[384]: <info>  [1655292393.7874] device (wlp0s20f0u3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 15 11:26:33 mamograg NetworkManager[384]: <info>  [1655292393.7880] dhcp4 (wlp0s20f0u3): activation: beginning transaction (timeout in 45 seconds)
…
Jun 15 11:26:35 mamograg NetworkManager[384]: <info>  [1655292395.4770] dhcp4 (wlp0s20f0u3): state changed new lease, address=192.168.1.104
…
Jun 15 11:26:35 mamograg NetworkManager[384]: <info>  [1655292395.6273] policy: set 'TP-LINK_905C3E' (wlp0s20f0u3) as default for IPv4 routing and DNS
…
Jun 15 11:26:36 mamograg NetworkManager[384]: <info>  [1655292396.3979] device (wlp0s20f0u3): Activation: successful, device activated.
…
Jun 15 11:26:39 mamograg NetworkManager[384]: <info>  [1655292399.3260] manager: NetworkManager state is now CONNECTED_GLOBAL

Starting 11:26:33 you got connected 11:26:39 to "TP-LINK_905C3E" which I assume is the desired connection?

The immediately

Jun 15 11:26:40 mamograg wpa_supplicant[425]: wlp3s0: SME: Trying to authenticate with 36:b2:0a:c3:36:f3 (SSID='Github' freq=2412 MHz)
…
Jun 15 11:26:41 mamograg wpa_supplicant[425]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 36:b2:0a:c3:36:f3 completed [id=0 id_str=]
…
Jun 15 11:26:53 mamograg wpa_supplicant[425]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=36:b2:0a:c3:36:f3 reason=3 locally_generated=1

you connect and 12 seconds later disconnect a second NIC to a different AP.

ip a; ip r

and why is there the second NIC trying to connect to a different AP?

mamograg17 · 2022-06-15 13:02:51

seth wrote:

and why is there the second NIC trying to connect to a different AP?

The second one is my built-in WiFi card, the second wifi network is my second wifi, i have to wifi networks

seth · 2022-06-15 13:20:14

The thing is that wlp0s20f0u3 (rtl8187) connects fine and then there's some diffuse action by the built-in chip.
Please post the "ip a; ip r" outputs and try to disable the built-in chip (I also guess it'll not connect to the "github" AP outside your home LAN?)

mamograg17 · 2022-06-15 13:53:55

seth wrote:

Please post the "ip a; ip r" outputs and try to disable the built-in chip (I also guess it'll not connect to the "github" AP outside your home LAN?)

ip a output:

╰─ ip a                                                                                                                                                                    ─╯
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether ac:e2:d3:04:25:84 brd ff:ff:ff:ff:ff:ff
    altname enp2s0
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether e8:4e:06:09:ea:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.104/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 259197sec preferred_lft 259197sec
4: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 6a:f4:52:71:77:e9 brd ff:ff:ff:ff:ff:ff permaddr d4:6a:6a:79:87:9b
5: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0

and this is ip r output:

╰─ ip r                                                                                                                                                                    ─╯
default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.104 metric 600 
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.104 metric 600

both the outputs are when i am connected to the wifi that doesn't work.

seth · 2022-06-15 14:08:11

The output names changed against the journal (did you https://wiki.archlinux.org/title/Networ … face_names ? In your case that's actually the exception where this isn't a good idea, because the wlan0/1 descriptors will take an unpredictable order. Though there's also the enp2s0 altname)

The other pink elephant in the room is of course the tunnel, so I'd suggest to try to disable whatever (likely) VPN that is.

mamograg17 · 2022-06-15 15:17:52

seth wrote:

The output names changed against the journal (did you https://wiki.archlinux.org/title/Networ … face_names ? In your case that's actually the exception where this isn't a good idea, because the wlan0/1 descriptors will take an unpredictable order. Though there's also the enp2s0 altname)
The other pink elephant in the room is of course the tunnel, so I'd suggest to try to disable whatever (likely) VPN that is.

Oh they changed by themselves, i didn't chane anything by myself, the wlan0 is the rtl8187, wlan1 is the builtin wifi card.

Last edited by mamograg17 (2022-06-15 15:18:11)

seth · 2022-06-15 18:47:03

seth wrote:

The other pink elephant in the room is of course the tunnel, so I'd suggest to try to disable whatever (likely) VPN that is.

I suggest to simplify the setup as much as possible (deactivate the internal wifi chip and skip the VPN) to figure whether this is really between the wifi chip and your AP or just the general environment of your home AP.

mamograg17 · 2022-06-15 20:17:30

seth wrote:

seth wrote:
The other pink elephant in the room is of course the tunnel, so I'd suggest to try to disable whatever (likely) VPN that is.
I suggest to simplify the setup as much as possible (deactivate the internal wifi chip and skip the VPN) to figure whether this is really between the wifi chip and your AP or just the general environment of your home AP.

Unfortunately, i figured out that the problem is not just with my home's wifi, i tried other networks like neighbor and restaurant one.

seth · 2022-06-15 20:27:20

Still: since the journal shows the chip to actually connect fine and because of the complications of the setup and especially iff the behavior ends up being somewhat heuristic: simplify the setup and try the chip in isolation.

mamograg17 · 2022-06-15 21:11:27

seth wrote:

Still: since the journal shows the chip to actually connect fine and because of the complications of the setup and especially iff the behavior ends up being somewhat heuristic: simplify the setup and try the chip in isolation.

I have disabled the builtin card, but still not working, is it the driver or what?

seth · 2022-06-16 06:10:18

"Destination Host Unreachable" generally means that the system doesn't know how to route the package from A to B what's not consistent w/ the output in #7
A driver error would rather lead to time-outs (and maybe some kernel messages) or - if the underlying cause is a connection failure/instable connection - reflected in an absent route (and probably lease) and in NMs case also a lot of kernel messages.

Did you also disable the VPN and what's the output for "ip a; ip r" and the system journal for such simplified boot?
Also

ip r get 8.8.8.8
ip r get 192.168.1.1

mamograg17 · 2022-06-16 09:34:59

seth wrote:

Did you also disable the VPN

yes

seth wrote:

ip r get 8.8.8.8

 ╰─ ip r get 8.8.8.8                                                                                                                                                        ─╯
8.8.8.8 via 192.168.1.1 dev wlan0 src 192.168.1.104 uid 1000 
    cache

seth wrote:

ip r get 192.168.1.1

 ╰─ ip r get 192.168.1.1                                                                                                                                                      ─╯
198.168.1.1 via 192.168.1.1 dev wlan0 src 192.168.1.104 uid 1000 
    cache

mamograg17 · 2022-06-16 10:08:13

seth wrote:

"Destination Host Unreachable" generally means that the system doesn't know how to route the package from A to B what's not consistent w/ the output in #7
A driver error would rather lead to time-outs (and maybe some kernel messages) or - if the underlying cause is a connection failure/instable connection - reflected in an absent route (and probably lease) and in NMs case also a lot of kernel messages.
Did you also disable the VPN and what's the output for "ip a; ip r" and the system journal for such simplified boot?
Also
ip r get 8.8.8.8
ip r get 192.168.1.1

does these informations help :

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    20600  0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     600    0        0 wlan0

and strangely, when i run route command when connected to the only wifi that works with this card, i get:

 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    601    0        0 wlan1
192.168.43.0    0.0.0.0         255.255.255.0   U     601    0        0 wlan1

Last edited by mamograg17 (2022-06-16 10:33:00)

seth · 2022-06-16 13:50:47

╰─ ip r get 192.168.1.1 ─╯
198.168.1.1 via 192.168.1.1 dev wlan0 src 192.168.1.104 uid 1000
cache

Literally???

The only thing that changes on the working NIC are the device (wlan0 -> wlan1) and the network segment (192.168.1.0 -> 192.168.43.0) - what is to be expected.
The metrics change isn't significant here.

Do you have a journal for the boot where you isolated the rtl8187 chip?
Also, just to be sure: using the rtl8187 on the secondary ("Github") AP fails and the built-in chip works fine w/ the TP-LINK_905C3E AP?

mamograg17 · 2022-06-16 14:01:36

seth wrote:

Also, just to be sure: using the rtl8187 on the secondary ("Github") AP fails and the built-in chip works fine w/ the TP-LINK_905C3E AP?

Github is a wifi extender, it takes Tp-link wifi and extend it, that's why its ip is 192.168.43.0.

Btw i found that the card supports wifi 802.11g only not 802.11n, is it the problem ?

seth · 2022-06-16 14:15:16

That doesn't answer the question.
Also we still need a journal of the isolated run.

Btw i found that the card supports wifi 802.11g only not 802.11n, is it the problem ?

According to your first journal you successfully associated w/ the AP and get a lease - the problem is somewhere else.

If you didn't have trouble pinging the _gateway I'd at this point say it's the router that's dropping the packages - though maybe it *is* the router, not responding to icmp requests either.
Then again: you said the problem extends to more APs…

Edit: you could also https://wiki.archlinux.org/title/Wireshark the failing pings

Last edited by seth (2022-06-16 14:19:03)

mamograg17 · 2022-06-16 15:10:50

seth wrote:

That doesn't answer the question.
Also we still need a journal of the isolated run.

here are the logs after disabling built-in card.
https://pastebin.com/BMCg5BXn

this is what i get when i ping _gateaway

╰─ ping _gateway                                                                                                                                                           ─╯
PING _gateway (192.168.1.1) 56(84) bytes of data.
^C
--- _gateway ping statistics ---
42 packets transmitted, 0 received, 100% packet loss, time 42010ms

Last edited by mamograg17 (2022-06-16 15:21:47)

seth · 2022-06-16 19:02:22

Sorry for the delay - had my own network problems, though no doubts about the cause (starts w/ "voda", ends with "fuck"…)

So thanks, this one's *far* more elaborate and shows some problems. Also the ping response has now changed.

Jun 16 15:01:24 mamograg NetworkManager[384]: <info>  [1655391684.2730] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 16 15:01:24 mamograg NetworkManager[384]: <info>  [1655391684.2771] manager: NetworkManager state is now CONNECTED_SITE
Jun 16 15:01:24 mamograg NetworkManager[384]: <info>  [1655391684.2777] policy: set 'TP-LINK_905C3E' (wlan0) as default for IPv4 routing and DNS
Jun 16 15:01:24 mamograg NetworkManager[384]: <info>  [1655391684.2846] device (wlan0): Activation: successful, device activated.
…
Jun 16 15:01:29 mamograg NetworkManager[384]: <info>  [1655391689.6881] manager: NetworkManager state is now CONNECTED_GLOBAL

You're connected to TP-LINK_905C3E \o/

Jun 16 15:01:42 mamograg plasmashell[1952]: kde.dataengine.weather: inexplicable failure of "bbcukmet|Tiznit, Morocco, MA"
Jun 16 15:01:42 mamograg NetworkManager[384]: <info>  [1655391702.3000] manager: NetworkManager state is now CONNECTED_SITE

Some problem, you're downgraded to a local connection, but no internet

Jun 16 15:01:49 mamograg NetworkManager[384]: <info>  [1655391709.1451] device (wlan0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
Jun 16 15:01:49 mamograg NetworkManager[384]: <info>  [1655391709.1468] manager: NetworkManager state is now DISCONNECTING
…
Jun 16 15:01:49 mamograg kernel: wlan0: deauthenticating from 98:48:27:90:5c:3e by local choice (Reason: 3=DEAUTH_LEAVING)
…
Jun 16 15:01:49 mamograg wpa_supplicant[424]: wlan0: CTRL-EVENT-DISCONNECTED bssid=98:48:27:90:5c:3e reason=3 locally_generated=1

You actively (? see below) disconnect from the network (perhaps to deal w/ the prev. situation)

Jun 16 15:01:55 mamograg wpa_supplicant[424]: wlan0: CTRL-EVENT-CONNECTED - Connection to 36:b2:0a:c3:36:f3 completed [id=0 id_str=]
…
Jun 16 15:01:55 mamograg NetworkManager[384]: <info>  [1655391715.9400] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2506] dhcp4 (wlan0): state changed new lease, address=192.168.43.186
…
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2933] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2937] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2942] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2950] manager: NetworkManager state is now CONNECTED_SITE
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2951] policy: set 'Github' (wlan0) as default for IPv4 routing and DNS
Jun 16 15:01:56 mamograg NetworkManager[384]: <info>  [1655391716.2956] device (wlan0): Activation: successful, device activated.
…
Jun 16 15:01:57 mamograg NetworkManager[384]: <info>  [1655391717.6330] manager: NetworkManager state is now CONNECTED_GLOBAL

You immediately and successfully connect to the "Github" AP \o/

Jun 16 15:02:38 mamograg wpa_supplicant[424]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-22 noise=9999 txrate=54000
…
Jun 16 15:03:19 mamograg wpa_supplicant[424]: wlan0: CTRL-EVENT-BEACON-LOSS

You've a very good signal and then lose the beacon 40s later.

This all smells power saving related. USB autosuspend is globally disabled by kernel parameter, but may still encounter https://wiki.archlinux.org/title/Networ … s#Cause_#1

mamograg17 · 2022-06-16 20:40:37

seth wrote:

This all smells power saving related. USB autosuspend is globally disabled by kernel parameter, but may still encounter https://wiki.archlinux.org/title/Networ … s#Cause_#1

Actually power saving is off, i think i have no more time to troubleshoot this problem, this card is amazing but it is somehow old,

Anyway thank you for your time, you Left your work to help me, that's really awesome, thank you,

The only thing that is strange is why does it work with wifi repeater but not to wifi router directly !?

seth · 2022-06-16 21:23:57

The beacon loss occurs on the Github SSID, on the TP-LINK_905C3E you disconnect for "reason 'user-requested'"

Looking at

Jun 16 15:01:29 mamograg NetworkManager[384]: <info>  [1655391689.6881] manager: NetworkManager state is now CONNECTED_GLOBAL
…
Jun 16 15:01:33 mamograg sudo[2521]: mamograg : TTY=pts/1 ; PWD=/home/mamograg ; USER=root ; COMMAND=/usr/bin/pacman --sync -y -u --
…
Jun 16 15:01:42 mamograg plasmashell[1952]: kde.dataengine.weather: inexplicable failure of "bbcukmet|Tiznit, Morocco, MA"
Jun 16 15:01:42 mamograg NetworkManager[384]: <info>  [1655391702.3000] manager: NetworkManager state is now CONNECTED_SITE

it would seem you connected, then ran pacman -Syu and 9 seconds later seem to have some network trouble.
Did pacman initially succeed to download packages?
https://bbs.archlinux.org/viewtopic.php … 7#p2022487

mamograg17 · 2022-06-16 21:27:59

seth wrote:

Did pacman initially succeed to download packages?
https://bbs.archlinux.org/viewtopic.php … 7#p2022487

No it didn't, i just tested if the wifi is working by doing an update,
And yeah the link didn't work, i tried what's in the comment by increasing the buffer but nothing changed.

Last edited by mamograg17 (2022-06-16 21:35:22)

seth · 2022-06-17 14:08:48

It would only have been relevant if the traffic got jammed under load.

The Router and Extender operate on the same channel, so it's not bluetooth interference.
The router signal isn't really bad, but the repeater is MUCH better, so that might be a factor (move closer to the router)

Also some APs really don't like https://wiki.archlinux.org/title/Networ … domization so you could deactivate that (though it would impact both NICs)
In general you could try to stop/disable NM and connect w/ wifi-menu (netctl package) to see whether the NM config is relevant.

Arch Linux

#1 2022-06-15 08:26:53

rtl8187 works with all other wifi networks except my home's one.

#2 2022-06-15 10:48:15

Re: rtl8187 works with all other wifi networks except my home's one.

#3 2022-06-15 11:39:54

Re: rtl8187 works with all other wifi networks except my home's one.

#4 2022-06-15 11:55:11

Re: rtl8187 works with all other wifi networks except my home's one.

#5 2022-06-15 13:02:51

Re: rtl8187 works with all other wifi networks except my home's one.

#6 2022-06-15 13:20:14

Re: rtl8187 works with all other wifi networks except my home's one.

#7 2022-06-15 13:53:55

Re: rtl8187 works with all other wifi networks except my home's one.

#8 2022-06-15 14:08:11

Re: rtl8187 works with all other wifi networks except my home's one.

#9 2022-06-15 15:17:52

Re: rtl8187 works with all other wifi networks except my home's one.

#10 2022-06-15 18:47:03

Re: rtl8187 works with all other wifi networks except my home's one.

#11 2022-06-15 20:17:30

Re: rtl8187 works with all other wifi networks except my home's one.

#12 2022-06-15 20:27:20

Re: rtl8187 works with all other wifi networks except my home's one.

#13 2022-06-15 21:11:27

Re: rtl8187 works with all other wifi networks except my home's one.

#14 2022-06-16 06:10:18

Re: rtl8187 works with all other wifi networks except my home's one.

#15 2022-06-16 09:34:59

Re: rtl8187 works with all other wifi networks except my home's one.

#16 2022-06-16 10:08:13

Re: rtl8187 works with all other wifi networks except my home's one.

#17 2022-06-16 13:50:47

Re: rtl8187 works with all other wifi networks except my home's one.

#18 2022-06-16 14:01:36

Re: rtl8187 works with all other wifi networks except my home's one.

#19 2022-06-16 14:15:16

Re: rtl8187 works with all other wifi networks except my home's one.

#20 2022-06-16 15:10:50

Re: rtl8187 works with all other wifi networks except my home's one.

#21 2022-06-16 19:02:22

Re: rtl8187 works with all other wifi networks except my home's one.

#22 2022-06-16 20:40:37

Re: rtl8187 works with all other wifi networks except my home's one.

#23 2022-06-16 21:23:57

Re: rtl8187 works with all other wifi networks except my home's one.

#24 2022-06-16 21:27:59

Re: rtl8187 works with all other wifi networks except my home's one.

#25 2022-06-17 14:08:48

Re: rtl8187 works with all other wifi networks except my home's one.

Board footer