Network Manager keeps disconnecting and reconnecting every few seconds

SWoL · 2024-08-22 16:34:29

Network Manager keeps disconnecting and reconnecting every 5-10 seconds or so. i used to be a fairly new Arch user up until a few months ago, then used Windows for a few months for personal reasons. Now that i switch back, Network Manager has the problem i mentioned above. I have tried a lot of the solutions on this forum, but none of them work for me. Everything used to be just fine a few months ago. i didn't change anything, re-installed everything the exact same way. I don't have any other Network Manager alternatives like dhcpcd or netcfg or netctl either. I installed the correct drivers, and everything works, but it just keeps disconnecting and reconnecting automatically. Please someone help.

Solution:

I reinstalled Arch for the 3rd time. Reinstalled the drivers and everything. Also factory reset my mom's phone. Still the issue persisted. Then I closely examined the system logs in realtime using "journalctl -ef". I was constantly getting deauthenticated right after connecting, with a message "(Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)".

$journalctl -ef

Aug 27 03:27:20 workstation systemd[923]: Started VTE child process 2291 launched by kgx process 1550.
Aug 27 03:27:59 workstation kernel: wlp3s0: deauthenticated from shit (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Aug 27 03:27:59 workstation wpa_supplicant[452]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=shit reason=7

The child process was me pinging www.google.com. Everytime I did it, the next 2 messages would follow and my internet would break.

So I googled this exact error, and tried many(almost 7-8) solutions. And the one that ended up working was:

https://ubuntuforums.org/showthread.php?t=2287034

This guy was getting the same problem, and he disabled power management for that particular device (in my case, it was wlp3s0) using iwconfig which is under the wireless_tools package in the default Arch repository. It worked for him. It worked for me as well. This is how i did it.

$ iwconfig

lo        no wireless extensions.

enp2s0    no wireless extensions.

enp4s0    no wireless extensions.

wlp3s0    IEEE 802.11  ESSID:"Redmi-8-MT"  
          Mode:Managed  Frequency:2.412 GHz  Access Point: shit  
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm  
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=54/70  Signal level=-56 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:226   Missed beacon:0

$ sudo iwconfig wlp3s0 power off

Now my internet doesn't disconnect and works flawlessly. I hope this works for someone.

Last edited by SWoL (2024-08-26 22:10:42)

Head_on_a_Stick · 2024-08-22 17:06:15

SWoL wrote:

I don't have any other Network Manager alternatives like dhcpcd or netcfg or netctl either. I installed the correct drivers

I don't believe you

Please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
lspci -knn -d ::02xx

SWoL · 2024-08-22 17:21:08

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

dbus-org.freedesktop.nm-dispatcher.service | system
getty@tty1.service                       | getty.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-userdbd.socket                   | sockets.target.wants

$ lspci -knn -d ::02xx

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
        Kernel driver in use: r8169
        Kernel modules: r8169
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller [10ec:b852]
        Kernel driver in use: rtw89_8852be
        Kernel modules: rtw89_8852be, 8852be, rtw_8852be
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
        Kernel driver in use: r8169
        Kernel modules: r8169

i apologize beforehand if i say anything wrong.

Last edited by SWoL (2024-08-22 17:22:22)

Head_on_a_Stick · 2024-08-22 17:27:46

SWoL wrote:

i apologize beforehand if i say anything wrong.

Don't be silly, say what you want. I am not offended easily.

SWoL wrote:

        Kernel driver in use: rtw89_8852be

I have that card and it works perfectly with just iwd

Try disabling MAC randomisation in NM, some routers really don't like that: https://wiki.archlinux.org/title/Networ … domization

Otherwise try these module parameters:

# /etc/modprobe.d/rtw89.conf
options rtw89_core disable_ps_mode=Y
options rtw89_pci disable_aspm_l1=Y disable_aspm_l1ss=Y

SWoL · 2024-08-22 17:53:37

Try disabling MAC randomisation in NM, some routers really don't like that

It's not a router man, it's an android mobile hotspot that i'm trying to connect to.

Otherwise try these module parameters:

# /etc/modprobe.d/rtw89.conf
options rtw89_core disable_ps_mode=Y
options rtw89_pci disable_aspm_l1=Y disable_aspm_l1ss=Y

I tried it, here's what's happening:

$ ping www.google.com
PING www.google.com (2404:6800:4002:821::2004) 56 data bytes
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=1 ttl=115 time=203 ms
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=2 ttl=115 time=227 ms
From workstation (shit) icmp_seq=27 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=28 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=29 Destination unreachable: Address unreachable
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=30 ttl=115 time=3051 ms
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=34 ttl=115 time=1017 ms
From workstation (shit) icmp_seq=70 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=71 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=72 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=76 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=77 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=78 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=79 Destination unreachable: Address unreachable
ping: sendmsg: No route to host
From workstation (shit) icmp_seq=80 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=81 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=83 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=84 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=85 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=86 Destination unreachable: Address unreachable
ping: sendmsg: No route to host
From workstation (shit) icmp_seq=87 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=88 Destination unreachable: Address unreachable
From _gateway (fe80::7c93:7eff:fe10:6620%wlp3s0) icmp_seq=100 Destination unreachable: Beyond scope of source address
From _gateway (fe80::7c93:7eff:fe10:6620%wlp3s0) icmp_seq=101 Destination unreachable: Beyond scope of source address
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=102 ttl=115 time=68.0 ms
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=103 ttl=115 time=167 ms
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=104 ttl=115 time=292 ms
64 bytes from del12s04-in-x04.1e100.net (2404:6800:4002:821::2004): icmp_seq=105 ttl=115 time=110 ms
^C
--- www.google.com ping statistics ---
118 packets transmitted, 8 received, +20 errors, 93.2203% packet loss, time 122607ms
rtt min/avg/max/mdev = 68.005/641.925/3050.549/953.102 ms, pipe 4

it just keeps automatically switching. i prefer not to turn off MAC randomization. i'll try iwd next, if it doesn't work i'll turn off MAC randomization.

Last edited by SWoL (2024-08-23 14:48:00)

SWoL · 2024-08-22 18:45:04

iwd doesn't help. it connects but the internet doesn't work.

i disabled MAC randomization and it doesn't disconnect anymore, but the internet speed has reduced to 1/100th of what it's supposed to be.

at this rate i might as well just reinstall the whole system from scratch.

Head_on_a_Stick · 2024-08-22 18:51:21

SWoL wrote:

iwd doesn't help. it connects but the internet doesn't work.

Did you enable the DHCP client?

https://wiki.archlinux.org/title/Iwd#En … figuration

Related: https://bbs.archlinux.org/viewtopic.php?id=57855

SWoL wrote:

at this rate i might as well just reinstall the whole system from scratch

We can fix this. Have faith

SWoL · 2024-08-23 10:53:23

done it. still didn't connect. first 2 times it shows "Operation Failed". the next 2 times doesn't show anything, just goes right to the [iwd]# prompt, but doesn't connect either.

should i try using systemd-networkd ?

Head_on_a_Stick · 2024-08-23 13:23:31

SWoL wrote:

done it. still didn't connect. first 2 times it shows "Operation Failed". the next 2 times doesn't show anything, just goes right to the [iwd]# prompt, but doesn't connect either

What is "it"? What shows that message? What exactly did you do to provoke that message?

Please try to understand that I cannot see what you are doing and so am relying on accurate reportage, without which decent assistance will be unlikely.

SWoL wrote:

should i try using systemd-networkd ?

That can't associate with wireless networks so it won't help here.

seth · 2024-08-23 13:42:05

Edit post #5 and obfuscate the IPv6 addresses that start w/ 2409:408 (it's a publically routable IPv6 in Mumbai)

then used Windows for a few months for personal reasons

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

Do NOT try to run iwd and NM in parallel, I'm not sold that this is a wpa_supplicant related issue, but if you want to try iwd, see https://wiki.archlinux.org/title/Networ … Fi_backend

Then please post your complete system journal for the boot:

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

There're two wired NICs?

ip a
ip r

Finally, just fyi

it's an android mobile hotspot that i'm trying to connect to

https://wiki.archlinux.org/title/Tethering

SWoL · 2024-08-23 15:20:23

What is "it"? What shows that message? What exactly did you do to provoke that message?

as per your instructions, i enabled dhcp in iwd by adding the following to my /etc/iwd/main.conf

[General]
EnableNetworkConfiguration=true

then i tried using iwd again, it detected my network, i tried to connect as per usual. but it just showed Operation failed after typing in the passphrase.

SWoL · 2024-08-23 15:37:47

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

i had it disabled long ago. also, my windows and linux systems are on entirely different SSDs, so i don't think it would matter even if it was on.

Then please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/XyVI.txt

There're two wired NICs?
ip a
ip r

here's the 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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether (shit) brd ff:ff:ff:ff:ff:ff
3: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether (shit) brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether (shit) brd ff:ff:ff:ff:ff:ff permaddr (shit)
    inet 192.168.43.236/24 brd (shit) scope global dynamic noprefixroute wlan0
       valid_lft 3491sec preferred_lft 3491sec
    inet6 (shit) scope global dynamic noprefixroute
       valid_lft 3371sec preferred_lft 3371sec
    inet6 (shit) scope link noprefixroute
       valid_lft forever preferred_lft forever
5: enp0s20f0u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether (shit) brd ff:ff:ff:ff:ff:ff permaddr (shit)
    inet 192.168.42.140/24 brd (shit) scope global dynamic noprefixroute enp0s20f0u2
       valid_lft 3206sec preferred_lft 3206sec
    inet6 (shit) scope link noprefixroute
       valid_lft forever preferred_lft forever

$ ip r

default via 192.168.42.129 dev enp0s20f0u2 proto dhcp src 192.168.42.140 metric 100
default via 192.168.43.1 dev wlan0 proto dhcp src 192.168.43.236 metric 600
192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.140 metric 100
192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.236 metric 600

also, since it's my mom's phone, i can't really use usb tethering, because she needs the phone.

seth · 2024-08-23 15:50:26

The stoarage location is utterly irrelevant, make sure it's still disabled since MS keeps enabling it with updates.
You've a parallel connection via some ethernet dongle, is that the tethering? Why is that there?

Either way, you connect, signal is excellent, then you get kicked

Aug 23 20:54:48 workstation kernel: wlan0: deauthenticated from 7e:93:7e:10:66:20 (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)

because you're sending data before being associated (what doesn't align with the local journal)
Then the phone doesn't let you in

Aug 23 20:54:53 workstation kernel: wlan0: authenticate with 7e:93:7e:10:66:20 (local address=72:fc:1e:d4:fa:92)
Aug 23 20:54:53 workstation kernel: wlan0: send auth to 7e:93:7e:10:66:20 (try 1/3)
Aug 23 20:54:53 workstation kernel: wlan0: send auth to 7e:93:7e:10:66:20 (try 2/3)
Aug 23 20:54:53 workstation kernel: wlan0: send auth to 7e:93:7e:10:66:20 (try 3/3)
Aug 23 20:54:53 workstation kernel: wlan0: authentication with 7e:93:7e:10:66:20 timed out

The dongle shows up

Aug 23 20:54:53 workstation NetworkManager[413]: <info>  [1724446493.5524] device (usb0): interface index 5 renamed iface from 'usb0' to 'enp0s20f0u2'

You connect again

Aug 23 20:54:58 workstation wpa_supplicant[436]: wlan0: CTRL-EVENT-CONNECTED - Connection to 7e:93:7e:10:66:20 completed [id=0 id_str=]

and get kicked for being lazy a minute later

Aug 23 20:55:56 workstation kernel: wlan0: disassociated from 7e:93:7e:10:66:20 (Reason: 4=DISASSOC_DUE_TO_INACTIVITY)

likely because the defaul route is now on enp0s20f0u2

And the phone ignores you again.

Do not try to use a second device and because of the initla kick double, triple and quadruple check that windows isn't hibernating, directly or through fast-start and reboot both OS twice or thrice (and if you can, the phone - once should do)

Then produce an updated journal that covers (several) disconnects *without* adding a second connection.
Do you have some AP to try (like your dad's phone or so )

Aug 23 20:55:56 workstation kernel: wlan0: authentication with 7e:93:7e:10:66:20 timed out

SWoL · 2024-08-23 16:26:10

rebooted windows, linux and the phone all 3 times. tried to connect again without adding any other connection. same thing is happening, disconnecting and reconnecting again. the usb tethering is for posting these replies, because the wireless network keeps disconnecting. dad is out of town, but he'll be coming back tomorrow night. i'll try with his phone too.

$ nmcli d wifi connect Redmi-8-MT password lolxd
Device 'wlan0' successfully activated with 'a940503f-8237-4c31-a878-4bea28d557f2'.

$ ping www.google.com
PING www.google.com (2404:6800:4002:826::2004) 56 data bytes
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=1 ttl=56 time=209 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=2 ttl=56 time=227 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=3 ttl=56 time=249 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=4 ttl=56 time=272 ms
From workstation (shit) icmp_seq=46 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=47 Destination unreachable: Address unreachable
From workstation (shit) icmp_seq=48 Destination unreachable: Address unreachable
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=49 ttl=56 time=1101 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=50 ttl=56 time=90.1 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=51 ttl=56 time=113 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=52 ttl=56 time=95.8 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=54 ttl=56 time=120 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=55 ttl=56 time=144 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=81 ttl=56 time=1378 ms
64 bytes from del12s09-in-x04.1e100.net (2404:6800:4002:826::2004): icmp_seq=82 ttl=56 time=393 ms
^C
--- www.google.com ping statistics ---
86 packets transmitted, 12 received, +3 errors, 86.0465% packet loss, time 86021ms
rtt min/avg/max/mdev = 90.075/366.002/1378.335/403.680 ms, pipe 2

it's usually 100-200 ms any time of day.

here's the system log:
http://0x0.st/XyWV.txt

i really appreciate this community for helping me with this.

Last edited by SWoL (2024-08-23 16:26:41)

SWoL · 2024-08-23 19:26:32

forget about it, I'm nuking my SSD. will reinstall system from scratch. if the same problem persists, I'll come back to this thread.

seth · 2024-08-23 19:32:49

Please notice that I'm not doing this 24/7, I came back like 10 minutes ago.

Re-installing is most likely not gonna do anything.

You keep getting kicked by the AP

Aug 23 21:42:34 workstation kernel: wlan0: authentication with 5a:c5:b5:24:d7:2d timed out
Aug 23 21:42:38 workstation kernel: wlan0: authenticate with 5a:c5:b5:24:d7:2d (local address=72:fc:1e:d4:fa:92)
Aug 23 21:42:38 workstation kernel: wlan0: send auth to 5a:c5:b5:24:d7:2d (try 1/3)
Aug 23 21:42:38 workstation kernel: wlan0: authenticated
Aug 23 21:42:38 workstation kernel: wlan0: associate with 5a:c5:b5:24:d7:2d (try 1/3)
Aug 23 21:42:38 workstation wpa_supplicant[435]: wlan0: CTRL-EVENT-CONNECTED - Connection to 5a:c5:b5:24:d7:2d completed [id=0 id_str=]
Aug 23 21:42:38 workstation wpa_supplicant[435]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=52000
Aug 23 21:43:09 workstation wpa_supplicant[435]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-42 noise=9999 txrate=65000
Aug 23 21:43:09 workstation wpa_supplicant[435]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=0 noise=9999 txrate=65000
Aug 23 21:43:17 workstation kernel: wlan0: deauthenticated from 5a:c5:b5:24:d7:2d (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
Aug 23 21:43:17 workstation wpa_supplicant[435]: wlan0: CTRL-EVENT-DISCONNECTED bssid=5a:c5:b5:24:d7:2d reason=7

If it's not a hibernating windows, disable MAC randomization. It doesn't matter whether you want to do this - you want to figure the cause, right?

SWoL · 2024-08-23 20:11:59

seth wrote:

Please notice that I'm not doing this 24/7, I came back like 10 minutes ago.

no no, please don't think that way. i don't expect everyone to always be here.

the reason i said that is because i remembered one key difference. back at the beginning of 2024 when i installed arch, i did NOT enable [multilib]. but in this recent install i did. i thought that's what must be screwing with everything. so i decided to reinstall.

If it's not a hibernating windows, disable MAC randomization. It doesn't matter whether you want to do this - you want to figure the cause, right?

already tried that above. it doesn't disconnect anymore, but the internet speed reduces to <2 KiB/s.

seth · 2024-08-23 20:18:16

[multilib]. but in this recent install i did. i thought that's what must be screwing with everything.

That is *extremely* unlikely.

it doesn't disconnect anymore, but the internet speed reduces to <2 KiB/s

Do you have a journal, and

iw dev wlan0 link
iw dev wlan0 station dump
ping -c8 google.com

for that context?
And wait for your dad (he doesn't have the same exact phone, does he?)

SWoL · 2024-08-26 22:11:08

Just posted the solution. Sorry it took so long, I had an exam today, so i was busy cramming for it. I was trying to add "[SOLVED]" to the title, but i couldn't.
Holy fuck. It feels good. I have the energy of a thousand suns.

Special thanks to seth and Head_on_a_Stick for helping me!!!

Head_on_a_Stick · 2024-08-27 05:48:19

The solution can be made permanent with a udev rule similar to https://wiki.archlinux.org/title/Power_ … interfaces but with the boolean reversed.

Arch Linux

#1 2024-08-22 16:34:29

Network Manager keeps disconnecting and reconnecting every few seconds

#2 2024-08-22 17:06:15

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#3 2024-08-22 17:21:08

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#4 2024-08-22 17:27:46

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#5 2024-08-22 17:53:37

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#6 2024-08-22 18:45:04

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#7 2024-08-22 18:51:21

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#8 2024-08-23 10:53:23

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#9 2024-08-23 13:23:31

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#10 2024-08-23 13:42:05

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#11 2024-08-23 15:20:23

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#12 2024-08-23 15:37:47

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#13 2024-08-23 15:50:26

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#14 2024-08-23 16:26:10

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#15 2024-08-23 19:26:32

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#16 2024-08-23 19:32:49

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#17 2024-08-23 20:11:59

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#18 2024-08-23 20:18:16

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#19 2024-08-26 22:11:08

Re: Network Manager keeps disconnecting and reconnecting every few seconds

#20 2024-08-27 05:48:19

Re: Network Manager keeps disconnecting and reconnecting every few seconds

Board footer