Constant wifi-drop

gasparov · 2018-01-09 11:39:29

Hi,
I have constant wifi drops, I've been trying to figure out the problem but I couldn't. Here are the lines in the log that keep repeating every second or so

Jan 09 11:29:49 gas-laptop NetworkManager[746]: <warn>  [1515497389.8684] sup-iface[0x564ad917f500,wlp7s0]: connection disconnected (reason 2)
Jan 09 11:29:49 gas-laptop kernel: wlp7s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
Jan 09 11:29:49 gas-laptop NetworkManager[746]: <info>  [1515497389.9028] device (wlp7s0): supplicant interface state: completed -> disconnected
Jan 09 11:29:49 gas-laptop NetworkManager[746]: <info>  [1515497389.9743] device (wlp7s0): supplicant interface state: disconnected -> scanning
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: SME: Trying to authenticate with 88:f0:77:36:a9:12 (SSID='XXX' freq=2437 MHz)
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: authenticate with 88:f0:77:36:a9:12
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: send auth to 88:f0:77:36:a9:12 (try 1/3)
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <info>  [1515497390.0363] device (wlp7s0): supplicant interface state: scanning -> authenticating
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: Trying to associate with 88:f0:77:36:a9:12 (SSID='XXX' freq=2437 MHz)
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: authenticated
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: associate with 88:f0:77:36:a9:12 (try 1/3)
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <info>  [1515497390.0489] device (wlp7s0): supplicant interface state: authenticating -> associating
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: RX AssocResp from 88:f0:77:36:a9:12 (capab=0x431 status=0 aid=171)
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: Associated with 88:f0:77:36:a9:12
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: associated
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <info>  [1515497390.0733] device (wlp7s0): supplicant interface state: associating -> 4-way handshake
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: WPA: Key negotiation completed with 88:f0:77:36:a9:12 [PTK=CCMP GTK=TKIP]
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to 88:f0:77:36:a9:12 completed [id=0 id_str=]
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <info>  [1515497390.0925] device (wlp7s0): supplicant interface state: 4-way handshake -> completed
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-53 noise=9999 txrate=1000
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: Limiting TX power to 14 dBm as advertised by 88:f0:77:36:a9:12
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: deauthenticated from 88:f0:77:36:a9:12 (Reason: 2=PREV_AUTH_NOT_VALID)
Jan 09 11:29:50 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=88:f0:77:36:a9:12 reason=2
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <warn>  [1515497390.9023] sup-iface[0x564ad917f500,wlp7s0]: connection disconnected (reason 2)
Jan 09 11:29:50 gas-laptop kernel: wlp7s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
Jan 09 11:29:50 gas-laptop NetworkManager[746]: <info>  [1515497390.9362] device (wlp7s0): supplicant interface state: completed -> disconnected
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <info>  [1515497391.0078] device (wlp7s0): supplicant interface state: disconnected -> scanning
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: SME: Trying to authenticate with 88:f0:77:36:a7:52 (SSID='XXX' freq=2412 MHz)
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: authenticate with 88:f0:77:36:a7:52
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: send auth to 88:f0:77:36:a7:52 (try 1/3)
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: Trying to associate with 88:f0:77:36:a7:52 (SSID='XXX' freq=2412 MHz)
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <info>  [1515497391.0992] device (wlp7s0): supplicant interface state: scanning -> authenticating
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: authenticated
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: associate with 88:f0:77:36:a7:52 (try 1/3)
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: RX AssocResp from 88:f0:77:36:a7:52 (capab=0x431 status=0 aid=117)
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <info>  [1515497391.1074] device (wlp7s0): supplicant interface state: authenticating -> associating
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: Associated with 88:f0:77:36:a7:52
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: associated
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <info>  [1515497391.1142] device (wlp7s0): supplicant interface state: associating -> 4-way handshake
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: WPA: Key negotiation completed with 88:f0:77:36:a7:52 [PTK=CCMP GTK=TKIP]
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to 88:f0:77:36:a7:52 completed [id=0 id_str=]
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <info>  [1515497391.1304] device (wlp7s0): supplicant interface state: 4-way handshake -> completed
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-46 noise=9999 txrate=57800
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: Limiting TX power to 14 dBm as advertised by 88:f0:77:36:a7:52
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: deauthenticated from 88:f0:77:36:a7:52 (Reason: 2=PREV_AUTH_NOT_VALID)
Jan 09 11:29:51 gas-laptop wpa_supplicant[1447]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=88:f0:77:36:a7:52 reason=2
Jan 09 11:29:51 gas-laptop NetworkManager[746]: <warn>  [1515497391.7133] sup-iface[0x564ad917f500,wlp7s0]: connection disconnected (reason 2)
Jan 09 11:29:51 gas-laptop kernel: wlp7s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

The wireless connection works sometimes even with those messages in the log, other time it simply drops. This is the wireless net of the office so I can't play with the router/AP. We have many AP in the room but from the log I see the same MAC address.
I have a Intel Corporation Dual Band Wireless AC 3160 and I use iwlwifi.
I tried also wicd + dhcpd or dhclient and I also have this problem.

lo1 · 2018-01-09 11:48:51

systemctl list-unit-files --state=enabled

gasparov · 2018-01-09 12:04:18

UNIT FILE                                   STATE  
org.cups.cupsd.path                         enabled
acpid.service                               enabled
autovt@.service                             enabled
avahi-daemon.service                        enabled
bluetooth.service                           enabled
cronie.service                              enabled
cups-browsed.service                        enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.Avahi.service          enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
fix-usb-wakeup.service                      enabled
getty@.service                              enabled
laptop-mode.service                         enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
nmbd.service                                enabled
org.cups.cupsd.service                      enabled
sddm.service                                enabled
smbd.service                                enabled
systemd-swap.service                        enabled
systemd-timesyncd.service                   enabled
teamviewerd.service                         enabled
winbindd.service                            enabled
avahi-daemon.socket                         enabled
org.cups.cupsd.socket                       enabled
remote-fs.target                            enabled
fstrim.timer                                enabled

lo1 · 2018-01-09 12:08:50

Try to stop NetworkManager for now and connect with wpa_supplicant, in a root shell and with the `-d` option set, then post the output here.

gasparov · 2018-01-09 12:37:31

Thanks Io1

lo1 wrote:

Try to stop NetworkManager for now and connect with wpa_supplicant, in a root shell and with the `-d` option set, then post the output here.

I've used pastebin if it's ok.
https://pastebin.com/XpjGx4JJ

I couldn't figure out much, but from line 240 on something happens, I get disconnected and the AP gets blacklisted

EDIT: I've found a similar situation, we also have Cisco APs... https://www.spinics.net/lists/linux-wir … 46814.html

Too bad there's no follow up

Last edited by gasparov (2018-01-09 13:27:12)

lo1 · 2018-01-09 13:37:35

You're welcome

Pastebin is perfect, just try to use something else than pastebin.com (see this)
I'll start throwing my guesses here: I don't know exactly how is wpa_supplicant managing security and if 802.1x include this behaviour, but

pastebin wrote:

Added BSSID 88:f0:77:36:a9:12 into blacklist
wlp7s0: Another BSS in this ESS has been seen; try it next

this mac-address is being inserted into a blacklist, probably just because your NIC is discovering other APs with the same mac-address (and it's trying to connect to the others as well?). As you said in the first post this is something you have already noted.

Now, I don't know if this is something specifically designed to avoid spoofing and weird behaviour inside a broadcast domain. You could try to enter `blacklist clear` inside a wpa_cli shell but that would just restart this endless loop.

nl80211: Deauthenticate event
wlp7s0: Event DEAUTH (12) received
wlp7s0: Deauthentication notification
wlp7s0:  * reason 2
wlp7s0:  * address 88:f0:77:36:a7:52

note that deauthentication reason is =2
https://www.cisco.com/assets/sol/sb/WAP … odes2.html

I think you should contact whoever is in charge of your office's network, if you're not the only one experiencing this issue.

gasparov · 2018-01-09 13:54:25

Thanks a lot...I think I'll do it, the problem is that they are not really inclined in helping people using linux.
As far as I can understand from the mailing list message I posted it's something related to cisco Aps that send deauth requests regularly, when that happens the ap gets blacklisted. I don't understand why these deauth requests are sent so often.
I'll keep this thread open and will go back if I find any solution

Arch Linux

#1 2018-01-09 11:39:29

Constant wifi-drop

#2 2018-01-09 11:48:51

Re: Constant wifi-drop

#3 2018-01-09 12:04:18

Re: Constant wifi-drop

#4 2018-01-09 12:08:50

Re: Constant wifi-drop

#5 2018-01-09 12:37:31

Re: Constant wifi-drop

#6 2018-01-09 13:37:35

Re: Constant wifi-drop

#7 2018-01-09 13:54:25

Re: Constant wifi-drop

Board footer