You are not logged in.
You can pass it to the kernel commandline as "iwlwifi.power_save=0" but also look at the journal (it's a bool and might prefer "iwlwifi.power_save=false")
Before that you can just try "iw dev wlan0 set power_save off"
Offline
I gave it a while to see how it would perform, but it still starts slowing down after a little while.
Here is a new journal:
https://pastebin.com/peFxLiW9
Offline
Oct 16 12:41:29 archlinux wpa_supplicant[562]: wlp0s20f3: SME: Trying to authenticate with 10:0c:6b:4c:8f:85 (SSID='Roberts2' freq=2442 MHz)
Oct 16 12:41:29 archlinux wpa_supplicant[562]: wlp0s20f3: Trying to associate with 10:0c:6b:4c:8f:85 (SSID='Roberts2' freq=2442 MHz)
Oct 16 12:58:04 archlinux wpa_supplicant[562]: wlp0s20f3: SME: Trying to authenticate with 10:0c:6b:47:2f:b8 (SSID='Roberts2' freq=2442 MHz)
Oct 16 12:58:05 archlinux wpa_supplicant[562]: wlp0s20f3: Trying to associate with 10:0c:6b:47:2f:b8 (SSID='Roberts2' freq=2442 MHz)Oct 16 12:58:04 archlinux wpa_supplicant[562]: wlp0s20f3: SME: Trying to authenticate with 10:0c:6b:47:2f:b8 (SSID='Roberts2' freq=2442 MHz)
Oct 16 12:58:04 archlinux kernel: wlp0s20f3: disconnect from AP 10:0c:6b:4c:8f:85 for new auth to 10:0c:6b:47:2f:b8
Oct 16 12:58:04 archlinux kernel: wlp0s20f3: authenticate with 10:0c:6b:47:2f:b8
Oct 16 12:58:04 archlinux kernel: wlp0s20f3: send auth to 10:0c:6b:47:2f:b8 (try 1/3)
Oct 16 12:58:04 archlinux kernel: wlp0s20f3: send auth to 10:0c:6b:47:2f:b8 (try 2/3)
Oct 16 12:58:05 archlinux kernel: wlp0s20f3: send auth to 10:0c:6b:47:2f:b8 (try 3/3)
Oct 16 12:58:05 archlinux wpa_supplicant[562]: wlp0s20f3: Trying to associate with 10:0c:6b:47:2f:b8 (SSID='Roberts2' freq=2442 MHz)
Oct 16 12:58:05 archlinux kernel: wlp0s20f3: associate with 10:0c:6b:47:2f:b8 (try 1/3)
Oct 16 12:58:05 archlinux kernel: wlp0s20f3: associate with 10:0c:6b:47:2f:b8 (try 2/3)
Oct 16 12:58:05 archlinux kernel: wlp0s20f3: associate with 10:0c:6b:47:2f:b8 (try 3/3)
Oct 16 12:58:05 archlinux kernel: wlp0s20f3: RX ReassocResp from 10:0c:6b:47:2f:b8 (capab=0x1411 status=0 aid=22)
Oct 16 12:58:05 archlinux wpa_supplicant[562]: wlp0s20f3: Associated with 10:0c:6b:47:2f:b8
Oct 16 12:58:05 archlinux wpa_supplicant[562]: wlp0s20f3: WPA: Key negotiation completed with 10:0c:6b:47:2f:b8 [PTK=CCMP GTK=CCMP]
Oct 16 12:58:05 archlinux wpa_supplicant[562]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 10:0c:6b:47:2f:b8 completed [id=0 id_str=]After ~16 minutes the AP seems to alter its BSSID, causing a re-connect?
Or are there repeaters in use?
Offline
Not sure what a reapeter is but I haven't set anything like that up. How can I fix this?
Offline
Range extender, different device w/ the same SSID.
If that's not the case and the AP is actively changing its BSSID for whatever reason, you need to "fix" that in the AP.
The client has to reconnect because the original AP is now gone (it seems)
The reconnect itself is a bit bumpy, but only takes 1 - 2 seconds
Offline