WiFi deteriorates with time

rpushin · 2024-05-06 14:23:14

I have an AMD desktop without wifi card. Currently running under Arch + KDE(plasma), with network manager provided with KDE, except from hanging when trying to sleep and wifi problem works fine.
I use TP-Link Archer T2UH (2.4+5) usb wifi adapter. Used it with windows previously, worked fine.

The problem is with time wifi connection deteriorates - speed becoming slower to the point of being unusable. Voice calls seem to work fine though, if I'm able to get into google meet despite the connection problems.
The problem seem to be dependent on quality of internet itself - when the connection is stable and fast this doesn't seem to occur. So I'm not even sure if anything that I do really affect the problem. But the other devices on the same network generally work much, much better. And it also seem that Linux Desktop also creates some problems for other devices when connected, but since all this happens only on unreliable connections - once again not sure, if it is so.

Disabling or deleting the network and reconnecting doesn't help. Changing browser(firefox-chromium) or closing or tabs don't help. Rebooting doesn't help. Changing SSID don't help either. Rebooting the router sometimes help. But problem arises with different routers, so don't expect the problem to be here
Using different USB-port helps for some time but after a while it deteriorates again.

Sometime ago used Outline.Appimage on this PC, but it totally destroyed even wired connection, so just deleted appimage file. Problem was occuring before experiments with Outline.

Link to journalctl -b
https://pastebin.com/v30Nm7wX

seth · 2024-05-07 16:17:01

with time wifi connection deteriorates … Voice calls seem to work fine though

Rebooting doesn't help. Changing SSID don't help either. Rebooting the router sometimes help.

And how do you reset the state so it can "deteriorate with time"?

May 06 16:59:52 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 06 16:59:52 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-CONNECTED - Connection to 50:ff:20:40:4f:75 completed [id=0 id_str=]
May 06 16:59:52 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-59 noise=9999 txrate=1000
May 06 16:59:54 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-BEACON-LOSS
…
May 06 17:01:42 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-CONNECTED - Connection to 78:a3:51:43:c1:88 completed [id=0 id_str=]
May 06 17:01:42 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-51 noise=9999 txrate=11000
May 06 17:02:06 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
May 06 17:02:25 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-20 noise=9999 txrate=135000
May 06 17:03:07 sosad wpa_supplicant[595]: wlp1s0f0u2: CTRL-EVENT-BEACON-LOSS

You're getting beacon-losses almost immediately. Not "over time".

May 06 16:58:29 sosad ntfs-3g[427]: Mounted /dev/sdb2 (Read-Write, label "Data", NTFS 3.1)

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

May 06 16:58:35 sosad NetworkManager[467]: <info>  [1715003915.2584] device (wlp1s0f0u2): set-hw-addr: set MAC address to 5A:D0:D4:6C:ED:AF (scanning)
May 06 16:59:07 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
May 06 16:59:50 sosad NetworkManager[467]: <info>  [1715003990.7953] Config: added 'scan_ssid' value '1'
May 06 16:59:50 sosad NetworkManager[467]: <info>  [1715003990.7954] Config: added 'bgscan' value 'simple:30:-70:86400'
May 06 16:59:50 sosad NetworkManager[467]: <info>  [1715003990.7956] device (wlp1s0f0u2): supplicant interface state: inactive -> scanning
May 06 16:59:50 sosad NetworkManager[467]: <info>  [1715003990.7956] device (p2p-dev-wlp1s0f0u2): supplicant management interface state: inactive -> scanning
May 06 16:59:52 sosad NetworkManager[467]: <info>  [1715003992.1636] device (wlp1s0f0u2): supplicant interface state: scanning -> authenticating
May 06 16:59:52 sosad NetworkManager[467]: <info>  [1715003992.1636] device (p2p-dev-wlp1s0f0u2): supplicant management interface state: scanning -> authenticating
May 06 17:00:51 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
May 06 17:01:31 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
May 06 17:01:38 sosad NetworkManager[467]: <info>  [1715004098.6881] device (wlp1s0f0u2): set-hw-addr: set MAC address to EE:FC:F1:E0:01:F9 (scanning)
May 06 17:01:41 sosad NetworkManager[467]: <info>  [1715004101.9604] Config: added 'scan_ssid' value '1'
May 06 17:01:41 sosad NetworkManager[467]: <info>  [1715004101.9605] Config: added 'bgscan' value 'simple:30:-70:86400'
May 06 17:02:03 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
May 06 17:02:18 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
May 06 17:02:48 sosad wpa_supplicant[595]: wlp1s0f0u2: Reject scan trigger since one is already pending
…

Stop/disable NM and try to connect w/ wifi-menu from netctl to avoid MAC spoofing and perma-scanning.
Are those connections more stable?

Arch Linux

#1 2024-05-06 14:23:14

WiFi deteriorates with time

#2 2024-05-07 16:17:01

Re: WiFi deteriorates with time

Board footer