[Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

josiano · 2018-06-05 13:02:55

Hello.
Coming back home after 3 months traveling I'm having troubles connecting to my wifi (I use NetworkManager and nm-applet):

- only after restarting my router I can connect to it
- if I put the computer to sleep, I cannot connect anymore
- if I (re)start the computer I cannot connect
- I can connect to any other wifi, always
- other linux distros connect to my wifi, always

I found a bunch of threads on google with that issue but none of the proposed solutions worked for me:
- disabling ipv6 did nothing
- using dhclient instead of dhcpcd didn't help
- manual connection (via wpa_supplicant) fails with

ioctl[SIOCSIWENCODEEXT]: Invalid argument

The error:

[ 1994.541097] wlp4s0: authenticate with 46:8d:36:6c:e7:42
[ 1994.551490] wlp4s0: send auth to 46:8d:36:6c:e7:42 (try 1/3)
[ 1994.557130] wlp4s0: authenticated
[ 1994.559714] wlp4s0: associate with 46:8d:36:6c:e7:42 (try 1/3)
[ 1994.562621] wlp4s0: RX AssocResp from 46:8d:36:6c:e7:42 (capab=0x1511 status=0 aid=49)
[ 1994.564833] wlp4s0: associated
[ 1994.608717] wlp4s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 46:8d:36:6c:e7:42
[ 1994.699742] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[ 2026.681714] wlp4s0: deauthenticating from 46:8d:36:6c:e7:42 by local choice (Reason: 3=DEAUTH_LEAVING)

My OS info:

$ uname -a
Linux x1carbon 4.16.13-1-ARCH #1 SMP PREEMPT Thu May 31 23:29:29 UTC 2018 x86_64 GNU/Linux

$ lspci | grep Network
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88)

I don't see conflicting services:

$ systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
bluetooth.service                           enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
getty@.service                              enabled
lxdm.service                                enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
vboxservice.service                         enabled
remote-fs.target                            enabled

12 unit files listed.

Interface isn't blocked:

$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Loaded kernel modules:

$ lsmod | grep wifi
iwlwifi               323584  1 iwlmvm
cfg80211              741376  3 iwlmvm,iwlwifi,mac80211

And in case, my connection info:

BSS 46:8d:36:6c:e7:42(on wlp4s0)
        last seen: 3101.815s [boottime]
        TSF: 985375044 usec (0d, 00:16:25)
        freq: 5180
        beacon interval: 100 TUs
        capability: ESS Privacy SpectrumMgmt ShortSlotTime RadioMeasure (0x1511)
        signal: -49.00 dBm
        last seen: 13376 ms ago
        Information elements from Probe Response frame:
        SSID: MiFibra-E73F-5G
        Supported rates: 6.0* 9.0 12.0* 18.0 24.0 36.0 48.0 54.0 
        DS Parameter set: channel 36
        BSS Load:
                 * station count: 3
                 * channel utilisation: 50/255
                 * available admission capacity: 65535 [*32us]
        Country: ES     Environment: Indoor/Outdoor
                Channels [36 - 36] @ 23 dBm
                Channels [40 - 40] @ 23 dBm
                Channels [44 - 44] @ 23 dBm
                Channels [48 - 48] @ 23 dBm
                Channels [52 - 52] @ 23 dBm
                Channels [56 - 56] @ 23 dBm
                Channels [60 - 60] @ 23 dBm
                Channels [64 - 64] @ 23 dBm
                Channels [100 - 100] @ 30 dBm
                Channels [104 - 104] @ 30 dBm
                Channels [108 - 108] @ 30 dBm
                Channels [112 - 112] @ 30 dBm
                Channels [116 - 116] @ 30 dBm
                Channels [120 - 120] @ 30 dBm
                Channels [124 - 124] @ 30 dBm
                Channels [128 - 128] @ 30 dBm
        Power constraint: 0 dB
        HT capabilities:
                Capabilities: 0x86f
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 4 usec (0x05)
                HT TX/RX MCS rate indexes supported: 0-31, 33-76
        HT operation:
                 * primary channel: 36
                 * secondary channel offset: above
                 * STA channel width: any
                 * RIFS: 0
                 * HT protection: no
                 * non-GF present: 1
                 * OBSS non-GF present: 0
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        WMM:     * Parameter version 1
                 * u-APSD
                 * BE: CW 15-63, AIFSN 4
                 * BK: CW 63-255, AIFSN 5
                 * VI: CW 15-63, AIFSN 4, TXOP 3008 usec
                 * VO: CW 7-31, AIFSN 3, TXOP 1504 usec
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        Extended capabilities:
                 * HT Information Exchange Supported
                 * BSS Transition
                 * SSID List
                 * Operating Mode Notification
                 * Max Number Of MSDUs In A-MSDU is unlimited
        VHT capabilities:
                VHT Capabilities (0x3fc37832):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        SU Beamformer
                        SU Beamformee
                        +HTC-VHT
                        RX antenna pattern consistency
                        TX antenna pattern consistency
                VHT RX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: MCS 0-9
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT RX highest supported: 0 Mbps
                VHT TX MCS set:
                        1 streams: MCS 0-9
                        2 streams: MCS 0-9
                        3 streams: MCS 0-9
                        4 streams: MCS 0-9
                        5 streams: not supported
                        6 streams: not supported
                        7 streams: not supported
                        8 streams: not supported
                VHT TX highest supported: 0 Mbps
        VHT operation:
                 * channel width: 1 (80 MHz)
                 * center freq segment 1: 42
                 * center freq segment 2: 0
                 * VHT basic MCS set: 0xfffc

Any help would be greatly appreciated as this is seriously driving me nuts.

Last edited by josiano (2018-06-05 18:14:29)

Trilby · 2018-06-05 13:27:03

Thanks for including all the relevant information - that makes it easier to get started. As a first check I'd recommend temporarily stoping/disabling any NetworkManager services and try using manual connection steps (e.g., wpa_supplicant + dhcpcd).

If those are able to connect/reconnect then we'd know the problem is restricted to NM, if they can't it may be more productive to look into the driver.

josiano · 2018-06-05 13:38:03

Manual connection fails at:

# wpa_supplicant -B -D wext -i wlp4s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument

My config reads:

~ » cat /etc/wpa_supplicant.conf                                                                                                                                                                                ~  
# reading passphrase from stdin
network={
	ssid="MiFibra-E73F-5G"
	#psk="..."
	psk=...
}

Trilby · 2018-06-05 13:48:57

Do you have reason to believe you need the '-D wext'? I've only ever seen specifying a -D flag cause problems, can you try without that?

josiano · 2018-06-05 14:07:40

No specific reason, just saw that it was recommended somewhere..

# wpa_supplicant -B -i wlp4s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
nl80211: Could not set interface 'p2p-dev-wlp4s0' UP
nl80211: deinit ifname=p2p-dev-wlp4s0 disabled_11b_rates=0
p2p-dev-wlp4s0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface

josiano · 2018-06-05 15:51:31

@Trilby sorry I forgot to kill the already running wpa_supplicant.
So, after changing the key for the clear text one it seems that wpa_supplicant is working:

# wpa_supplicant -i wlp4s0 -c /etc/wpa_supplicant.conf                                         ~  
Successfully initialized wpa_supplicant
...
wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp4s0: WPA: Key negotiation completed with ... [PTK=CCMP GTK=CCMP]
wlp4s0: CTRL-EVENT-CONNECTED - Connection to ... completed [id=0 id_str=]

but still no luck:

$ ping 8.8.8.8
connect: Network is unreachable

Last edited by josiano (2018-06-05 15:52:12)

Trilby · 2018-06-05 16:27:36

That's progress. After wpa_supplicant is "Successfully initialized" you still need to get an IP address. Most often this is done with dhcpcd:

# dhcpcd wlp4s0

josiano · 2018-06-05 17:57:53

Thanks. After running dhcpcd it works.

josiano · 2018-06-05 18:13:55

Ah, after switching to wicd it seems to work like a charm, so I guess there must be a bug in NetworkManager..
I wish someone would confirm this though..

Anyway, my issue is resolved, thank you Trilby for your time and help!

V1del · 2018-06-05 20:01:50

More likely a bug in NetworkManager's internal dhcp, I'm not entirely sure why that has been made a default by the NM devs with so many issues, should be fixable with e.g.: https://wiki.archlinux.org/index.php/Ne … HCP_client

Arch Linux

#1 2018-06-05 13:02:55

[Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#2 2018-06-05 13:27:03

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#3 2018-06-05 13:38:03

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#4 2018-06-05 13:48:57

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#5 2018-06-05 14:07:40

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#6 2018-06-05 15:51:31

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#7 2018-06-05 16:27:36

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#8 2018-06-05 17:57:53

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#9 2018-06-05 18:13:55

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

#10 2018-06-05 20:01:50

Re: [Solved] Cannot connect to home wifi (DEAUTH_LEAVING)

Board footer