Endless Wi-Fi disconnect and reconnent

lyceux · 2017-04-14 22:50:30

When my laptop starts up, either from off or just restarting, my wifi works great without a hitch. But for some reason after a random amount of time (sometimes after a few minutes, sometimes after a few hours), I will no longer be able to connect to anything. (I use NetworkManager with gnome and the wifi stays connected but shows a little question mark on it). This happens on multiple different networks I've tried with different types of router hardware. My laptop has a ATH9K (AR9462, 2.4GHz only, wireless N).

Journalctl shows this log:

12:14:36 wpa_supplicant[436]: wlp59s0: WPA: Key negotiation completed with 18:d2:76:83:58:70 [PTK=CCMP GTK=CCMP]
12:14:36 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-CONNECTED - Connection to 18:d2:76:83:58:70 completed [id=0 id_str=]
12:14:36 NetworkManager[381]: <info>  [1492128876.9103] device (wlp59s0): supplicant interface state: 4-way handshake -> completed
12:14:47 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-DISCONNECTED bssid=18:d2:76:83:58:70 reason=4 locally_generated=1
12:14:47 NetworkManager[381]: <warn>  [1492128887.0270] sup-iface[0xe65d90,wlp59s0]: connection disconnected (reason -4)
12:14:47 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
12:14:47 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=NZ
12:14:47 NetworkManager[381]: <info>  [1492128887.0597] device (wlp59s0): supplicant interface state: completed -> disconnected
12:14:47 NetworkManager[381]: <info>  [1492128887.1328] device (wlp59s0): supplicant interface state: disconnected -> scanning
12:14:50 wpa_supplicant[436]: wlp59s0: SME: Trying to authenticate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
12:14:50 kernel: wlp59s0: authenticate with 18:d2:76:83:58:70
12:14:50 NetworkManager[381]: <info>  [1492128890.8317] device (wlp59s0): supplicant interface state: scanning -> authenticating
12:14:50 wpa_supplicant[436]: wlp59s0: Trying to associate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
12:14:50 kernel: wlp59s0: send auth to 18:d2:76:83:58:70 (try 1/3)
12:14:50 kernel: wlp59s0: authenticated
12:14:50 kernel: wlp59s0: associate with 18:d2:76:83:58:70 (try 1/3)
12:14:50 wpa_supplicant[436]: wlp59s0: Associated with 18:d2:76:83:58:70
12:14:50 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
12:14:50 NetworkManager[381]: <info>  [1492128890.8389] device (wlp59s0): supplicant interface state: authenticating -> associated
12:14:50 kernel: wlp59s0: RX AssocResp from 18:d2:76:83:58:70 (capab=0x411 status=0 aid=5)
12:14:50 kernel: wlp59s0: associated
12:14:50 NetworkManager[381]: <info>  [1492128890.8551] device (wlp59s0): supplicant interface state: associated -> 4-way handshake
12:14:50 wpa_supplicant[436]: wlp59s0: WPA: Key negotiation completed with 18:d2:76:83:58:70 [PTK=CCMP GTK=CCMP]
12:14:50 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-CONNECTED - Connection to 18:d2:76:83:58:70 completed [id=0 id_str=]
12:14:50 NetworkManager[381]: <info>  [1492128890.8703] device (wlp59s0): supplicant interface state: 4-way handshake -> completed
12:14:54 wpa_supplicant[436]: wlp59s0: CTRL-EVENT-DISCONNECTED bssid=18:d2:76:83:58:70 reason=4 locally_generated=1
12:14:55 NetworkManager[381]: <warn>  [1492128895.0002] sup-iface[0xe65d90,wlp59s0]: connection disconnected (reason -4)

I was wondering if NetworkManager or wpa_supplicant were at fault, so I tried disabling them and using wifi-menu with dhcpcd instead, but that just produced essentially the exact same result (worked for awhile and then connection loop):

10:26:34 kernel: wlp59s0: authenticate with 18:d2:76:83:58:70
10:26:34 kernel: wlp59s0: send auth to 18:d2:76:83:58:70 (try 1/3)
10:26:34 kernel: wlp59s0: authenticated
10:26:34 kernel: wlp59s0: associate with 18:d2:76:83:58:70 (try 1/3)
10:26:34 kernel: wlp59s0: RX AssocResp from 18:d2:76:83:58:70 (capab=0x411 status=0 aid=5)
10:26:34 kernel: wlp59s0: associated
10:26:34 dhcpcd[7133]: wlp59s0: carrier acquired
10:26:34 dhcpcd[7133]: wlp59s0: IAID 89:74:61:03
10:26:35 dhcpcd[7133]: wlp59s0: rebinding lease of 192.168.1.5
10:26:35 dhcpcd[7133]: wlp59s0: probing address 192.168.1.5/24
10:26:39 dhcpcd[7133]: wlp59s0: leased 192.168.1.5 for 86400 seconds
10:26:39 dhcpcd[7133]: wlp59s0: adding route to 192.168.1.0/24
10:26:39 dhcpcd[7133]: wlp59s0: adding default route via 192.168.1.1
10:26:54 dhcpcd[7133]: wlp59s0: carrier lost
10:26:54 dhcpcd[7133]: wlp59s0: deleting default route via 192.168.1.1
10:26:54 dhcpcd[7133]: wlp59s0: deleting route to 192.168.1.0/24
10:26:58 kernel: wlp59s0: authenticate with 18:d2:76:83:58:70
10:26:58 kernel: wlp59s0: send auth to 18:d2:76:83:58:70 (try 1/3)
10:26:58 kernel: wlp59s0: authenticated
10:26:58 kernel: wlp59s0: associate with 18:d2:76:83:58:70 (try 1/3)
10:26:58 kernel: wlp59s0: RX AssocResp from 18:d2:76:83:58:70 (capab=0x411 status=0 aid=5)
10:26:58 kernel: wlp59s0: associated
10:26:58 dhcpcd[7133]: wlp59s0: carrier acquired
10:26:58 dhcpcd[7133]: wlp59s0: IAID 89:74:61:03
10:26:59 dhcpcd[7133]: wlp59s0: rebinding lease of 192.168.1.5
10:26:59 dhcpcd[7133]: wlp59s0: probing address 192.168.1.5/24

That basically repeats endlessly, connecting, then immediately disconnecting, and trying to reconnect, over and over.

Trying to trace route to archlinux.org produced this, it seems to be able to work a little bit for a few seconds between the reconnects.

Host                                                                                                      Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.1.1                                                                                            95.9%   148    1.9   2.4   1.9   3.8   0.4
 2. lo0.internet.ivpn.pe14.telstraclear.net                                                                95.2%   148   46.3  70.1  46.3 174.1  47.2
 3. ie2-g-0-0-0.telstraclear.net                                                                           95.2%   148   54.0  64.3  53.0 104.2  18.7
 4. ge-0-2-0-1.xcore1.acld.telstraclear.net                                                                95.2%   148   81.9  66.1  53.8  97.0  17.1
 5. gi2-20.akl-grafton-bdr1.ihug.net                                                                       95.2%   148   55.3  54.4  53.8  55.3   0.0
 6. 10.123.80.69                                                                                           95.9%   148  178.5 178.4 177.5 179.1   0.0
 7. 216.218.254.57                                                                                         95.9%   148  187.3 182.5 178.3 189.4   4.9
 8. 10ge7-2.core1.sjc2.he.net                                                                              96.6%   148  206.4 194.1 177.4 206.4  14.1
 9. 100ge1-2.core1.nyc4.he.net                                                                             96.6%   148  262.9 247.5 240.9 262.9   9.1
10. 100ge4-1.core1.par2.he.net                                                                             98.0%   148  318.9 329.9 317.6 353.1  20.1
11. 100ge5-2.core1.fra1.he.net                                                                             98.0%   148  321.5 320.4 319.8 321.5   0.7
12. 80.81.193.164                                                                                          98.0%   148  329.5 329.3 329.1 329.5   0.0
13. 213.239.203.150                                                                                        97.3%   148  326.6 335.1 326.2 358.6  15.7
14. ex9k2.rz17.hetzner.de                                                                                  97.9%   147  337.0 336.0 335.5 337.0   0.7
15. apollo.archlinux.org                                                                                   97.1%   138  335.4 336.4 335.4 336.8   0.6

Sleeping doesn't seem to affect it at all, it will wake up and continue working just fine (when it was working before sleep), and will also stop working without the computer having slept at all since boot. The only way I've found to remedy it is just to restart the machine, disconnecting and reconnecting, toggling airplane mode, or restarting the services doesn't seem to solve the problem. Any help would be much appreciated, thanks

jasonwryan · 2017-04-14 22:56:10

Please paste the output of:

systemctl list-unit-files --state enabled

lyceux · 2017-04-14 23:01:45

UNIT FILE                                   STATE  
autovt@.service                             enabled
bumblebeed.service                          enabled
dbus-fi.w1.wpa_supplicant1.service          enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
gdm.service                                 enabled
getty@.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
sshguard.service                            enabled
systemd-timesyncd.service                   enabled
wpa_supplicant.service                      enabled
remote-fs.target                            enabled

14 unit files listed.

jasonwryan · 2017-04-14 23:22:27

Disable both NM and wpa_supplicant services and connect manually: see if that results in a stable connection.

lyceux · 2017-04-14 23:24:05

I already tried doing that initially, and connecting with wifi-menu, but it has the same problem. (The journal log is up in the first post)

jasonwryan · 2017-04-14 23:27:54

wifi-menu is not a manual connection...

lyceux · 2017-04-15 00:23:44

Sorry, I've not used a manual connection before so I'm not entirely sure on the specifics. I disabled NetworkManager and wpa_supplicant services, and followed https://wiki.archlinux.org/index.php/Wi … nual_setup on connecting using iw and wpa_supplicant from terminal. Is this the correct way? I am currently connected and there aren't any problems so far, but they sometimes take up to an hour to appear.

jasonwryan · 2017-04-15 01:58:18

Yes. That's the correct approach. If you don't experience any issues after a couple of hours, then it can be narrowed down to the tools.

lyceux · 2017-04-15 02:42:47

Two hours in, no dice unfortunately, the same thing happened again.

wlp59s0: CTRL-EVENT-CONNECTED - Connection to 18:d2:76:83:58:70 completed [id=0 id_str=]
wlp59s0: CTRL-EVENT-DISCONNECTED bssid=18:d2:76:83:58:70 reason=4 locally_generated=1
wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=NZ
wlp59s0: SME: Trying to authenticate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
wlp59s0: Trying to associate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
wlp59s0: Associated with 18:d2:76:83:58:70
wlp59s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp59s0: WPA: Key negotiation completed with 18:d2:76:83:58:70 [PTK=CCMP GTK=CCMP]
wlp59s0: CTRL-EVENT-CONNECTED - Connection to 18:d2:76:83:58:70 completed [id=0 id_str=]
wlp59s0: CTRL-EVENT-DISCONNECTED bssid=18:d2:76:83:58:70 reason=4 locally_generated=1
wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlp59s0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=NZ
wlp59s0: SME: Trying to authenticate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
wlp59s0: Trying to associate with 18:d2:76:83:58:70 (SSID='vodafone5869' freq=2437 MHz)
wlp59s0: Associated with 18:d2:76:83:58:70
wlp59s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp59s0: WPA: Key negotiation completed with 18:d2:76:83:58:70 [PTK=CCMP GTK=CCMP]
wlp59s0: CTRL-EVENT-CONNECTED - Connection to 18:d2:76:83:58:70 completed [id=0 id_str=]
wlp59s0: CTRL-EVENT-DISCONNECTED bssid=18:d2:76:83:58:70 reason=4 locally_generated=1

14:36:29 kernel: wlp59s0: authenticate with 18:d2:76:83:58:70
14:36:29 kernel: wlp59s0: send auth to 18:d2:76:83:58:70 (try 1/3)
14:36:29 kernel: wlp59s0: authenticated
14:36:29 kernel: wlp59s0: associate with 18:d2:76:83:58:70 (try 1/3)
14:36:29 kernel: wlp59s0: RX AssocResp from 18:d2:76:83:58:70 (capab=0x411 status=0 aid=5)
14:36:29 kernel: wlp59s0: associated
14:36:29 dhcpcd[3102]: wlp59s0: carrier acquired
14:36:29 dhcpcd[3102]: wlp59s0: IAID 89:74:61:03
14:36:29 dhcpcd[3102]: wlp59s0: soliciting an IPv6 router
14:36:30 dhcpcd[3102]: wlp59s0: Router Advertisement from fe80::1
14:36:30 dhcpcd[3102]: wlp59s0: adding address fd18:d276:8358:6900:6342:dad6:7527:77d/64
14:36:30 dhcpcd[3102]: wlp59s0: adding route to fd18:d276:8358:6900::/64
14:36:30 dhcpcd[3102]: wlp59s0: requesting DHCPv6 information
14:36:30 dhcpcd[3102]: wlp59s0: rebinding lease of 192.168.1.5
14:36:30 dhcpcd[3102]: wlp59s0: probing address 192.168.1.5/24
14:36:30 geoclue[796]: Failed to query location: Could not connect: Network is unreachable
14:36:34 dhcpcd[3102]: wlp59s0: leased 192.168.1.5 for 86400 seconds
14:36:34 dhcpcd[3102]: wlp59s0: adding route to 192.168.1.0/24
14:36:34 dhcpcd[3102]: wlp59s0: adding default route via 192.168.1.1
14:36:44 dhcpcd[3102]: wlp59s0: carrier lost
14:36:44 dhcpcd[3102]: wlp59s0: deleting address fd18:d276:8358:6900:6342:dad6:7527:77d/64
14:36:44 dhcpcd[3102]: wlp59s0: deleting route to fd18:d276:8358:6900::/64
14:36:44 dhcpcd[3102]: wlp59s0: deleting default route via 192.168.1.1
14:36:44 dhcpcd[3102]: wlp59s0: deleting route to 192.168.1.0/24
14:36:48 kernel: wlp59s0: authenticate with 18:d2:76:83:58:70
14:36:48 kernel: wlp59s0: send auth to 18:d2:76:83:58:70 (try 1/3)
14:36:48 kernel: wlp59s0: authenticated
14:36:48 kernel: wlp59s0: associate with 18:d2:76:83:58:70 (try 1/3)
14:36:48 kernel: wlp59s0: RX AssocResp from 18:d2:76:83:58:70 (capab=0x411 status=0 aid=5)
14:36:48 kernel: wlp59s0: associated

jasonwryan · 2017-04-15 04:21:03

Seems a known issue with your card: there are a couple of fixes/workarounds suggested here
https://bbs.archlinux.org/viewtopic.php?id=159290

lyceux · 2017-04-15 05:26:27

Yeah I found that thread while searching the problem initially, but nohwcrypt=1 didn't help at all, and they fixed their problem by ditching NetworkManager and using wifi-menu (to prevent the scan issue), which didn't help me either.

jasonwryan · 2017-04-15 05:46:49

There are other options to try: https://wiki.archlinux.org/index.php/ASUS_E403SA#Wi-Fi

lyceux · 2017-04-15 05:54:11

Oh I'll give that a try and see how it goes, thanks!

r0b0t · 2017-09-30 14:51:13

Well, I have a

04:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01)
	Subsystem: AzureWave AR9462 Wireless Network Adapter

I never had the disconnection problem until yesterday when I upgraded [2017-09-29 21:32] [ALPM] upgraded linux (4.12.13-1 -> 4.13.3-1)
After I reverted back to 4.12.13-1 everything is good so far and no disconnections (normally it should have already happen by now).

Arch Linux

#1 2017-04-14 22:50:30

Endless Wi-Fi disconnect and reconnent

#2 2017-04-14 22:56:10

Re: Endless Wi-Fi disconnect and reconnent

#3 2017-04-14 23:01:45

Re: Endless Wi-Fi disconnect and reconnent

#4 2017-04-14 23:22:27

Re: Endless Wi-Fi disconnect and reconnent

#5 2017-04-14 23:24:05

Re: Endless Wi-Fi disconnect and reconnent

#6 2017-04-14 23:27:54

Re: Endless Wi-Fi disconnect and reconnent

#7 2017-04-15 00:23:44

Re: Endless Wi-Fi disconnect and reconnent

#8 2017-04-15 01:58:18

Re: Endless Wi-Fi disconnect and reconnent

#9 2017-04-15 02:42:47

Re: Endless Wi-Fi disconnect and reconnent

#10 2017-04-15 04:21:03

Re: Endless Wi-Fi disconnect and reconnent

#11 2017-04-15 05:26:27

Re: Endless Wi-Fi disconnect and reconnent

#12 2017-04-15 05:46:49

Re: Endless Wi-Fi disconnect and reconnent

#13 2017-04-15 05:54:11

Re: Endless Wi-Fi disconnect and reconnent

#14 2017-09-30 14:51:13

Re: Endless Wi-Fi disconnect and reconnent

Board footer