frequent network disconnects with wpa_supplicant

6r4y · 2025-08-04 11:31:15

I'm using a thinkpad e16 gen 2, which has a realtek RTL8852BE. I manage wifi using wpa_supplicant and wpa_cli, and have not had any issues for a couple of months.
After i connected to the wifi of a camping, it started repeatedly disconnecting from the wifi, stating `CTRL-EVENT-DISCONNECTED bssid=[ip address] reason=4 locally_generated=1`. after looking around i discovered that that means its disconnecting due to inactivity. this was unexpected as this also happens when i am actively using the wifi. I updated all packages, i tried using iw to disable power saving (i couldnt find anything for wpa to do that), and i installed a different version of the driver, specifically rtw89_8852be, from the aur. the issue has not been resolved yet and i can find little information about it online or on here. This issue also occurs on 4g hotstops, so its not an issue with the wifi, and it doesnt happen consistently. sometimes it works perfectly (like right now, which i am using to write this topic), but then it randomly disconnects and tries finding the network again, then reconnects and disconnects a number of times before settling.

6r4y · 2025-08-04 11:55:13

Ok so my bluetooth followed with the random disconnects, so i thought it might have been ny network card that was loose, but i checked and thats not it. Its not loose at all

seth · 2025-08-04 15:19:59

Please don't bump - edit your previous post to mend it if nobody has yet replied to not feign action on the thread.
Also please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Do you have the system journal of an affected boot, eg.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous ("-1") one?

6r4y · 2025-08-04 15:57:27

https://0x0.st/8hX9.txt
the disconnect happens around 17:46:50.

seth · 2025-08-04 21:19:51

ACPI action undefined: PNP0C0A:00

There's 1200+ lines of that - it's probably your charger? Is it loose? Does the network stabilize on battery?

6r4y · 2025-08-04 21:23:39

not being on charger does not stabilize it.

seth · 2025-08-04 21:28:14

Can you post that journal (just to confirm that at least the ACPI events are gone and thus just a red herring - and not actually not the charger)
Edit: oh, and please run wpa_supplicant w/ -dd - see https://man.archlinux.org/man/wpa_supplicant.8#d

Last edited by seth (2025-08-04 21:29:51)

6r4y · 2025-08-04 21:51:13

https://0x0.st/8hZ0.txt
first disconnect happened at 23:39:28

seth · 2025-08-04 22:18:28

Aug 04 23:39:10 hugo-thorium systemd-networkd[441]: wlp2s0: DHCPv4 address and routes set.
Aug 04 23:39:10 hugo-thorium systemd-networkd[441]: wlp2s0: link_check_ready(): IPv4LL:no DHCPv4:yes DHCPv6:no DHCP-PD:no NDisc:no
Aug 04 23:39:10 hugo-thorium systemd-networkd[441]: wlp2s0: State changed: configuring -> configured
Aug 04 23:39:11 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 7s
Aug 04 23:39:18 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: No RA received before link confirmation timeout
Aug 04 23:39:18 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Invoking callback for 'timeout' event.
Aug 04 23:39:18 hugo-thorium systemd-networkd[441]: wlp2s0: NDisc handler get timeout event
Aug 04 23:39:18 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 15s
Aug 04 23:39:28 hugo-thorium kernel: wlp2s0: Connection to AP f0:9f:c2:3d:15:1e lost
Aug 04 23:39:28 hugo-thorium systemd-networkd[441]: wlp2s0: Flags change: -LOWER_UP -RUNNING
Aug 04 23:39:28 hugo-thorium systemd-networkd[441]: wlp2s0: Lost carrier
…
Aug 04 23:39:33 hugo-thorium systemd-networkd[441]: wlp2s0: DHCPv4 address and routes set.
Aug 04 23:39:33 hugo-thorium systemd-networkd[441]: wlp2s0: link_check_ready(): IPv4LL:no DHCPv4:yes DHCPv6:no DHCP-PD:no NDisc:no
Aug 04 23:39:33 hugo-thorium systemd-networkd[441]: wlp2s0: State changed: configuring -> configured
Aug 04 23:39:34 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 3s
Aug 04 23:39:38 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 8s
Aug 04 23:39:44 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: No RA received before link confirmation timeout
Aug 04 23:39:44 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Invoking callback for 'timeout' event.
Aug 04 23:39:44 hugo-thorium systemd-networkd[441]: wlp2s0: NDisc handler get timeout event
Aug 04 23:39:46 hugo-thorium systemd-networkd[441]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 15s
Aug 04 23:39:57 hugo-thorium systemd-networkd[441]: wlp2s0: Flags change: -LOWER_UP -RUNNING
Aug 04 23:39:57 hugo-thorium kernel: wlp2s0: Connection to AP f0:9f:c2:3d:15:1e lost
Aug 04 23:39:57 hugo-thorium systemd-networkd[441]: wlp2s0: Lost carrier

There's no proper communication after the (itself untroubled) connection at all.
If you stop networkd and connect w/ wifi-menu from the netctl package (it'll invoke wpa_supplicant and dhcpcd itself), do you maintain a stable connection?

The run in that journal was btw, not w/ -dd, was it?

Edit: btw. Nivaa Camping2.4G is the AP you mentioned in the OP, right?
For clarification: does this also happen w/ other APs or have you currently only tested this one?
Can you try to connect to eg. your phones hotspot?

Last edited by seth (2025-08-04 22:20:32)

6r4y · 2025-08-05 09:31:13

wifi-menu did not stabilize the connection, i used -ddd, and yes it does happen on other networks, namely a phone hotspot.

seth · 2025-08-05 14:23:24

i used -ddd

Not sure whether the 3rd d does anything, but you'd expect to see signal quality reports etc. from wpa_supplicant when activating the debug output.
But if you're starting the daemon from an interactive shell the output might only get there (and if you're starting it while an instance is already running you're probably not starting it at all)

rn. there's no explanation for the behavior, you're connecting w/o issues and then the connection is lost after ~25s (coincidentally? the dbus timeout)
There're no indications of HW failure nor issues w/ the connection and 25s is too quick(?) to be related to https://wiki.archlinux.org/title/Power_ … interfaces ?
You could still try https://bbs.archlinux.org/viewtopic.php … 3#p2249033 …

6r4y · 2025-08-05 21:52:43

kernel paramneters didn't work, but after locating wpa's logs in var/log/wpa_supplicant i found this:

...
1754427696.599300: wlp2s0: Control interface command 'PING'
1754427696.599313: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=5
1754427701.603925: Control interface recv command from: /tmp/wpa_ctrl_1359-1\x00
1754427701.603967: wlp2s0: Control interface command 'PING'
1754427701.603989: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=5
1754427701.715627: RTM_NEWLINK: ifi_index=3 ifname=wlp2s0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
1754427701.813828: nl80211: Event message available
1754427701.813865: nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlp2s0
1754427701.813873: nl80211: Delete station f0:9f:c2:3d:15:1e
1754427701.818553: nl80211: Event message available
1754427701.818574: nl80211: Drv Event 39 (NL80211_CMD_DEAUTHENTICATE) received for wlp2s0 
...

It appears to be working fine and then get an 802.11 message to remove the station? i dont know what to do with the

Event message available

i cant find much about an "event message" for nl80211.

seth · 2025-08-06 09:47:17

wpa_supplicant -s -t -d …

shall log w/ debug into the system journal (in doubt use networkmanager, it will activate wpa_suppplicant debug into the system log), interspersed with the other events and then please post the journal, not random log lines.
The snippet looks like an ICMP request timed out and then disconnected.

6r4y · 2025-08-06 13:42:54

here is the journal with wpa supplicant
https://0x0.st/8hVW.txt
at 15:34:42 it "gained carrier" (which i assume means it connected), and at 15:34:45 it "lost carrier" (vice versa).

seth · 2025-08-06 17:04:00

Aug 06 15:34:29 hugo-thorium kernel: wlp2s0: Connection to AP f0:9f:c2:3d:15:1e lost
Aug 06 15:34:29 hugo-thorium systemd-networkd[458]: wlp2s0: Lost carrier
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: wlp2s0: BSS: Remove id 0 BSSID f0:9f:c2:3d:15:1e SSID 'Nivaa Camping2.4G' due to Connection to AP lost
Aug 06 15:34:32 hugo-thorium systemd-networkd[458]: wlp2s0: DHCP lease lost
Aug 06 15:34:45 hugo-thorium kernel: wlp2s0: Connection to AP b4:fb:e4:14:39:2e lost
Aug 06 15:34:45 hugo-thorium systemd-networkd[458]: wlp2s0: Lost carrier
Aug 06 15:34:45 hugo-thorium wpa_supplicant[707]: wlp2s0: BSS: Remove id 1 BSSID b4:fb:e4:14:39:2e SSID 'Nivaa Camping2.4G' due to Connection to AP lost

1st loss looks like human intervention (sudo wpa_cli

Aug 06 15:33:31 hugo-thorium systemd-networkd[458]: wlp2s0: LLDP Rx: Invoking callback for 'added' event.
Aug 06 15:33:31 hugo-thorium systemd-networkd[458]: wlp2s0: LLDP Rx: Successfully processed LLDP datagram.
Aug 06 15:33:44 hugo-thorium systemd-networkd[458]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 31s
Aug 06 15:33:45 hugo-thorium wpa_supplicant[707]: l2_packet_receive: src=18:e8:29:13:77:44 len=64
Aug 06 15:33:45 hugo-thorium wpa_supplicant[707]: TDLS: Received Data frame encapsulation - hexdump(len=64): 01 f0 1a 00 18 e8 29 14 77 44 d4 e7 b6 13 fd 16 99 8d 48 ec 4d a8 7b 6c ae 2e 0b 02 76 80 9c 5c 1c 97 a3 32 3e 49 9e 4a 68 14 58 c7 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 06 15:33:45 hugo-thorium wpa_supplicant[707]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Aug 06 15:34:00 hugo-thorium wpa_supplicant[707]: l2_packet_receive: src=b4:fb:e4:13:39:2e len=64
Aug 06 15:34:00 hugo-thorium wpa_supplicant[707]: TDLS: Received Data frame encapsulation - hexdump(len=64): 01 f0 1a 00 b4 fb e4 15 39 2e d7 57 1c 0f 17 ac 6e ef 47 25 83 fb 56 fb dc 2c af 4e 81 1c 4b 01 98 d0 cf 9a 50 08 b5 63 86 87 fe a1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Aug 06 15:34:00 hugo-thorium wpa_supplicant[707]: TDLS: Invalid frame - payloadtype=1 category=240 action=26
Aug 06 15:34:01 hugo-thorium systemd-networkd[458]: wlp2s0: LLDP Rx: Invoking callback for 'refreshed' event.
Aug 06 15:34:01 hugo-thorium systemd-networkd[458]: wlp2s0: LLDP Rx: Successfully processed LLDP datagram.
Aug 06 15:34:02 hugo-thorium sudo[1655]:     hugo : TTY=pts/1 ; PWD=/home/hugo ; USER=root ; COMMAND=/usr/bin/wpa_cli
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL_IFACE monitor attached /tmp/wpa_ctrl_1666-2\x00
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=3
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=96
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: Control interface recv command from: /tmp/wpa_ctrl_1666-1\x00
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: wlp2s0: Control interface command 'LIST_CREDS'
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=43
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: Control interface recv command from: /tmp/wpa_ctrl_1666-1\x00
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: wlp2s0: Control interface command 'LIST_NETWORKS'
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=165
Aug 06 15:34:02 hugo-thorium wpa_supplicant[707]: CTRL-DEBUG: ctrl_sock-sendto: sock=13 sndbuf=212992 outq=0 send_len=5
Aug 06 15:34:15 hugo-thorium systemd-networkd[458]: wlp2s0: NDISC: Sent Router Solicitation, next solicitation in 1min 5s
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: RTM_NEWLINK: ifi_index=3 ifname=wlp2s0 operstate=2 linkmode=1 ifi_family=0 ifi_flags=0x1003 ([UP])
Aug 06 15:34:29 hugo-thorium kernel: wlp2s0: Connection to AP f0:9f:c2:3d:15:1e lost
Aug 06 15:34:29 hugo-thorium systemd-networkd[458]: wlp2s0: Flags change: -LOWER_UP -RUNNING
Aug 06 15:34:29 hugo-thorium systemd-networkd[458]: wlp2s0: Lost carrier
Aug 06 15:34:29 hugo-thorium systemd-networkd[458]: wlp2s0: nl80211: received del_station(20) message: bssid=f0:9f:c2:3d:15:1e
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: nl80211: Event message available
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: nl80211: Drv Event 20 (NL80211_CMD_DEL_STATION) received for wlp2s0
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: nl80211: Delete station f0:9f:c2:3d:15:1e
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: nl80211: Event message available
Aug 06 15:34:29 hugo-thorium systemd-networkd[458]: wlp2s0: nl80211: received deauthenticate(39) message.
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: nl80211: Drv Event 39 (NL80211_CMD_DEAUTHENTICATE) received for wlp2s0

Second one might be the same (you'd still have sudo creds) - what did you wpa_cli there?

Edit

Aug 06 15:33:14 hugo-thorium kernel: wlp2s0: associated
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: nl80211: Associated on 2412 MHz
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: nl80211: Associated with f0:9f:c2:3d:15:1e
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated to a new BSS: BSSID=f0:9f:c2:3d:15:1e
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with f0:9f:c2:3d:15:1e
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: wlp2s0: State: ASSOCIATED -> 4WAY_HANDSHAKE
…
Aug 06 15:34:02 hugo-thorium sudo[1655]:     hugo : TTY=pts/1 ; PWD=/home/hugo ; USER=root ; COMMAND=/usr/bin/wpa_cli
…
Aug 06 15:34:39 hugo-thorium kernel: wlp2s0: associated
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: nl80211: Associated on 2462 MHz
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: nl80211: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated to a new BSS: BSSID=b4:fb:e4:14:39:2e
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: wlp2s0: State: ASSOCIATED -> 4WAY_HANDSHAKE
Aug 06 15:34:49 hugo-thorium kernel: wlp2s0: associated
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: nl80211: Associated on 2462 MHz
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: nl80211: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated to a new BSS: BSSID=b4:fb:e4:14:39:2e
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: wlp2s0: State: ASSOCIATED -> 4WAY_HANDSHAKE

This is after the first association.

Last edited by seth (2025-08-06 17:07:40)

6r4y · 2025-08-06 17:17:33

First one might have been because of me, but i just opened wpacli to see the output of wpa_supplicant. Second one was definitely a legit disconnect.

seth · 2025-08-06 19:47:34

Aug 06 15:33:13 hugo-thorium wpa_supplicant[707]: wlp2s0: SME: Trying to authenticate with f0:9f:c2:3d:15:1e (SSID='Nivaa Camping2.4G' freq=2412 MHz)
Aug 06 15:33:13 hugo-thorium wpa_supplicant[707]: wlp2s0: Trying to associate with f0:9f:c2:3d:15:1e (SSID='Nivaa Camping2.4G' freq=2412 MHz)
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: nl80211: Associated with f0:9f:c2:3d:15:1e
Aug 06 15:33:14 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with f0:9f:c2:3d:15:1e
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: wlp2s0:  * reason 4 (DISASSOC_DUE_TO_INACTIVITY) locally_generated=1
Aug 06 15:34:29 hugo-thorium wpa_supplicant[707]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=f0:9f:c2:3d:15:1e reason=4 locally_generated=1
Aug 06 15:34:38 hugo-thorium wpa_supplicant[707]: wlp2s0: SME: Trying to authenticate with b4:fb:e4:14:39:2e (SSID='Nivaa Camping2.4G' freq=2462 MHz)
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: wlp2s0: Trying to associate with b4:fb:e4:14:39:2e (SSID='Nivaa Camping2.4G' freq=2462 MHz)
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: nl80211: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:39 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:45 hugo-thorium wpa_supplicant[707]: wlp2s0:  * reason 4 (DISASSOC_DUE_TO_INACTIVITY) locally_generated=1
Aug 06 15:34:45 hugo-thorium wpa_supplicant[707]: wlp2s0: CTRL-EVENT-DISCONNECTED bssid=b4:fb:e4:14:39:2e reason=4 locally_generated=1
Aug 06 15:34:48 hugo-thorium wpa_supplicant[707]: wlp2s0: SME: Trying to authenticate with b4:fb:e4:14:39:2e (SSID='Nivaa Camping2.4G' freq=2462 MHz)
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: wlp2s0: Trying to associate with b4:fb:e4:14:39:2e (SSID='Nivaa Camping2.4G' freq=2462 MHz)
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: nl80211: Associated with b4:fb:e4:14:39:2e
Aug 06 15:34:49 hugo-thorium wpa_supplicant[707]: wlp2s0: Associated with b4:fb:e4:14:39:2e

The first one actually changes the AP (maybe it altered its frequency?)

https://bbs.archlinux.org/viewtopic.php?id=298748 had the same setup/problem fixed by (effectively)

iw dev wlp2s0 set power_save off

(so still power saving related)

6r4y · 2025-08-06 20:49:41

iwconfig shows:

lo        no wireless extensions.

enp1s0    no wireless extensions.

wlp2s0    IEEE 802.11  ESSID:"Nivaa Camping2.4G"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: F0:9F:C2:3D:15:1E   
          Bit Rate=26 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=31/70  Signal level=-79 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:22   Missed beacon:0

power management is already off, and has been since at least the second journal i sent. if there is another power saving im missing id be happy to try, but i dont think that is it

seth · 2025-08-07 06:29:51

Link Quality=31/70 Signal level=-79 dBm

Why is the signal so poor? (-79dBm is incredibly bad and random minor interference will cut the communication)
What does the situation actually look like when you connect to your phones hotspot in ultimate proximity?

Also try to rfkill bluetooth (which operates in the 2.4GHz band and might be the cause of the poor signal?)

6r4y · 2025-08-09 16:07:27

ok so using dhcpcd to automatically start wpa_supplicant, and only connecting through my phones hotspot, the issue seems to have been resolved. i will update if this works on other wifi networks when i get home from vacation

seth · 2025-08-09 17:25:05

I assume you've a much better signal to your phone?

seth wrote:

Why is the signal so poor?

Distance? Interference? Forgot to plug a stub antenna?

Arch Linux

#1 2025-08-04 11:31:15

frequent network disconnects with wpa_supplicant

#2 2025-08-04 11:55:13

Re: frequent network disconnects with wpa_supplicant

#3 2025-08-04 15:19:59

Re: frequent network disconnects with wpa_supplicant

#4 2025-08-04 15:57:27

Re: frequent network disconnects with wpa_supplicant

#5 2025-08-04 21:19:51

Re: frequent network disconnects with wpa_supplicant

#6 2025-08-04 21:23:39

Re: frequent network disconnects with wpa_supplicant

#7 2025-08-04 21:28:14

Re: frequent network disconnects with wpa_supplicant

#8 2025-08-04 21:51:13

Re: frequent network disconnects with wpa_supplicant

#9 2025-08-04 22:18:28

Re: frequent network disconnects with wpa_supplicant

#10 2025-08-05 09:31:13

Re: frequent network disconnects with wpa_supplicant

#11 2025-08-05 14:23:24

Re: frequent network disconnects with wpa_supplicant

#12 2025-08-05 21:52:43

Re: frequent network disconnects with wpa_supplicant

#13 2025-08-06 09:47:17

Re: frequent network disconnects with wpa_supplicant

#14 2025-08-06 13:42:54

Re: frequent network disconnects with wpa_supplicant

#15 2025-08-06 17:04:00

Re: frequent network disconnects with wpa_supplicant

#16 2025-08-06 17:17:33

Re: frequent network disconnects with wpa_supplicant

#17 2025-08-06 19:47:34

Re: frequent network disconnects with wpa_supplicant

#18 2025-08-06 20:49:41

Re: frequent network disconnects with wpa_supplicant

#19 2025-08-07 06:29:51

Re: frequent network disconnects with wpa_supplicant

#20 2025-08-09 16:07:27

Re: frequent network disconnects with wpa_supplicant

#21 2025-08-09 17:25:05

Re: frequent network disconnects with wpa_supplicant

Board footer