wireless link not ready (4way_handshake_timeout)

sharethewisdom · 2018-01-23 09:17:07

Little more than a week ago, I started having trouble with my wireless internet connection when I rebooted. I read about a kernel bug, so I updated the system, and tried both linux and linux-tls. I un-blacklisted some modules, and turned off usb power-saving. I don't remember exactly what else I changed when playing with power-saving measures.

uname -a

    Linux libreboot 4.14.13-1-ARCH #1 SMP PREEMPT Wed Jan 10 11:14:50 UTC 2018 x86_64 GNU/Linux

systemctl list-unit-files --state enabled

    UNIT FILE              STATE
    org.cups.cupsd.path    enabled
    acpid.service          enabled
    autovt@.service        enabled
    cpupower.service       enabled
    getty@.service         enabled
    lm_sensors.service     enabled
    nftables.service       enabled
    org.cups.cupsd.service enabled
    org.cups.cupsd.socket  enabled
    remote-fs.target       enabled
    10 unit files listed.

see this paste for kernel warnings and errors. This is dmesg|grep -i net:

[    0.116671] NET: Registered protocol family 16
[    0.164315] NetLabel: Initializing
[    0.164317] NetLabel:  domain hash size = 128
[    0.164318] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.164349] NetLabel:  unlabeled traffic allowed by default
[    0.197315] NET: Registered protocol family 2
[    0.198063] NET: Registered protocol family 1
[    0.691614] NET: Registered protocol family 10
[    0.698084] NET: Registered protocol family 17
[    2.961275] NET: Registered protocol family 38
[   10.359558] ip_tables: (C) 2000-2006 Netfilter Core Team
[   11.427548] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[   11.437862] thinkpad_acpi: http://ibm-acpi.sf.net/
[   11.599097] NET: Registered protocol family 31
[   11.675751] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[   12.347536] Netfilter messages via NETLINK v0.30.
[   12.357434] nf_tables: (c) 2007-2009 Patrick McHardy <kaber@trash.net>
[   13.337183] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[  532.660038] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1103.508285] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

for the full pacman log, see this paste

The messages in the journal right after booting are similar like the ones below. I'm using netctl-auto, but I guess that doesn't matter.

I noticed and commented out the contents of this file:

cat /etc/systemd/system/netctl@home.service.d/override.conf

    [Service]
    TimeoutStartSec=100

and ran

systemctl daemon-reload
ip link set wlp2s0 down
systemctl restart netctl-auto@wlp2s0.service

but the problem persists (again, 4way_handshake_timeout):

journalctl -xo cat -S-5s|uniq

    wlp2s0: authenticate with 68:15:90:0a:99:10
    wlp2s0: send auth to 68:15:90:0a:99:10 (try 1/3)
    wlp2s0: authenticated
    wlp2s0: associate with 68:15:90:0a:99:10 (try 1/3)
    wlp2s0: RX AssocResp from 68:15:90:0a:99:10 (capab=0x411 status=0 aid=2)
    wlp2s0: associated
    wlp2s0: deauthenticated from 68:15:90:0a:99:10 (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)

This is profile used while writing this post. I tried the uncommented settings and went through many reboots.

cat /etc/netctl/home

Description='home'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=WiFi-2.4-990a
IP=dhcp
Key=XXXXXXXXX
NETCTL_DEBUG=yes
# Timeout=100
# TimeoutCarrier=100
# IP6=stateless
# revise this setting:
# SkipDAD=yes

hardware: lspci|grep Wireless

    02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

I found only little information about the handshake timeout.

(rant) I think that another shameful point of frustration to beginners like me is that searching for the meaning of a *NO CARRIER* status seems to return anything but a clear definition; either in the manuals, the wiki, the forums, or online. I realize that this seems evident for most users. Please agree to providing a small reference in the wiki.

lo1 · 2018-01-23 10:08:13

+1 for the "NO CARRIER" confusion on the web, even if I don't agree totally with the rant: writing a bunch of things about "NO CARRIER" in the wiki will just led to an endless chain of "if a try this, if b try this, if c try this...". Shortly, NO-CARRIER is no information at all.

Since you're aware that this is a 4 way handshake timeout, let's assume that CARRIER is your EAP authenticator (your access point), keep netctl out of the equation, connect manually with wpa_supplicant using the debug option and post the output here.

Is the driver ath9k?

modinfo ath9k  #or equivalent
systool -avm ath9k

sharethewisdom · 2018-01-23 19:23:02

yes, I use ath9k

modinfo ath9k|grep -v alias

filename:       /lib/modules/4.14.13-1-ARCH/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko.xz
license:        Dual BSD/GPL
description:    Support for Atheros 802.11n wireless LAN cards.
author:         Atheros Communications
srcversion:     7D17CC093F34F0B0EFAE62D
depends:        mac80211,ath9k_hw,ath9k_common,cfg80211,ath,led-class
intree:         Y
name:           ath9k
vermagic:       4.14.13-1-ARCH SMP preempt mod_unload modversions 
parm:           debug:Debugging mask (uint)
parm:           nohwcrypt:Disable hardware encryption (int)
parm:           blink:Enable LED blink on activity (int)
parm:           led_active_high:Invert LED polarity (int)
parm:           btcoex_enable:Enable wifi-BT coexistence (int)
parm:           bt_ant_diversity:Enable WLAN/BT RX antenna diversity (int)
parm:           ps_enable:Enable WLAN PowerSave (int)

I forgot to include rfkill output:

ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0     blocked unblocked
 1 wlan      phy0   unblocked unblocked

in a quick test dhcpcd times out for both ipv4 and ipv6

# systemctl stop netctl-auto@wlp2s0.service
# ip link set wlp2s0 up
# dhcpcd -x enp0s25
# wpa_supplicant -B -i wlp2s0 -c <(wpa_passphrase WiFi-2.4-990a myPassphrase)
# dhcpcd -K4 wlp2s0
# dhcpcd -K6 wlp2s0

I tried to add tls_disable_tlsv1_[1,2]=1, see https://bbs.archlinuxcn.org/viewtopic.p … 055#p23055, but to be honest I have no idea why. I'm tired and I'll continue trying to solve this and test other access points later (next week probably). I also tried to add the regulatory domain.

cat /etc/wpa_supplicant/wpa_supplicant.conf

network={
  ssid="WiFi-2.4-990a"
  psk=a7829171a5473c7236bb8...
  #phase1="tls_disable_tlsv1_1=1 tls_disable_tlsv1_2=1"
  #phase2="auth=MSCHAPv2"
}
country=BE

# wpa_supplicant -B -i wlp2s0 -ddd -c /etc/wpa_supplicant/wpa_supplicant.conf -f w2.log

I've spent hours doing different things. w2.log has 2151927 lines, it keeps on scanning for access points.

Here are some snippets. Should I really post the whole thing?

wlp2s0: 1: 68:15:90:0a:99:10 ssid='WiFi-2.4-990a' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-58 freq=2437  wps
wlp2s0:    skip - blacklisted (count=2 limit=0)
...
wlp2s0: No APs found - clear blacklist and try again
Removed BSSID 68:15:90:0a:99:10 from blacklist (clear)
...
wlp2s0: SME: Association request to the driver failed
...
Added BSSID 68:15:90:0a:99:10 into blacklist
Continuous association failures - consider temporary network disabling

router AP

BSS 68:15:90:0a:99:10(on wlp2s0)
  TSF: 2888238728759 usec (33d, 10:17:18)
  freq: 2437
  beacon interval: 100 TUs
  capability: ESS Privacy ShortSlotTime (0x0411)
  signal: -76.00 dBm
  last seen: 636 ms ago
  Information elements from Probe Response frame:
  SSID: WiFi-2.4-990a
  Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0 
  DS Parameter set: channel 6
  ERP: <no flags>
  Extended supported rates: 6.0 9.0 12.0 48.0 
  RSN:   * Version: 1
     * Group cipher: CCMP
     * Pairwise ciphers: CCMP
     * Authentication suites: PSK
     * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
  BSS Load:
     * station count: 1
     * channel utilisation: 50/255
     * available admission capacity: 0 [*32us]
  HT capabilities:
    Capabilities: 0x83c
      HT20
      SM Power Save disabled
      RX Greenfield
      RX HT20 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: 8 usec (0x06)
    HT RX MCS rate indexes supported: 0-15
    HT TX MCS rate indexes are undefined
  HT operation:
     * primary channel: 6
     * secondary channel offset: no secondary
     * STA channel width: 20 MHz
     * RIFS: 1
     * 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
  Extended capabilities:
     * Extended Channel Switching
     * BSS Transition
     * Operating Mode Notification
  WPS:   * Version: 1.0
     * Wi-Fi Protected Setup State: 2 (Configured)
     * Response Type: 3 (AP)
     * UUID: d96c7efc-2f89-38f1-efbd-6e5148bfa812
     * Manufacturer: SagemCom
     * Model: SagemcomFast3865b_BBOX3
     * Model Number: S.2.0-1.0
     * Serial Number: LK14072DP361277
     * Primary Device Type: 6-0050f204-1
     * Device name: SagemcomFast3865b_BBOX3-LK14
     * Config methods: Label, Display
     * RF Bands: 0x1
     * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
  WMM:   * Parameter version 1
     * u-APSD
     * BE: CW 15-1023, AIFSN 3
     * BK: CW 15-1023, AIFSN 7
     * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
     * VO: CW 3-7, AIFSN 2, TXOP 1504 usec

seth · 2018-01-23 21:47:20

Try reloading ath9k w/ nohwcrypt=1 (that's probably why lo1 asked for the running modules attributes)
Does the password contain non-ascii characters?

lo1 · 2018-01-23 22:02:16

in a quick test dhcpcd times out for both ipv4 and ipv6

This is normal if you can't even complete the handshake and associate with an AP (didn't you, right?)

I tried to add tls_disable_tlsv1_[1,2]=1, see https://bbs.archlinuxcn.org/viewtopic.p … 055#p23055, but to be honest I have no idea why.

tls = Transport Layer Security, don't bother about it if you can't see any changes by either enabling or disabling it. Just remember to add quotes around your psk if it contains spaces.

Here are some snippets. Should I really post the whole thing?

Not really, at this point I don't know what good can it be, leave aside understanding that wpa_supplicant is a very talkative tool.
For the next time, connect just like this:

wpa_supplicant -d -i wlp2s0 -c<(wpa_passphrase "yourssid" "yourpsk")

The thing is, from your wpa_supplicant -ddd output:

wlp2s0: 1: 68:15:90:0a:99:10 ssid='WiFi-2.4-990a' wpa_ie_len=0 rsn_ie_len=20 caps=0x411 level=-58 freq=2437  wps
wlp2s0:    skip - blacklisted (count=2 limit=0)
wlp2s0: No APs found - clear blacklist and try again

if you can confirm that this AP works well with other devices, you should double check if the password is right and attempt anything suggested by https://wiki.archlinux.org/index.php/Wi … tion#ath9k

If you own the router, temporarily disable the password and try to connect without any kind of security, as a sanity check to make sure that your NIC is still capable of "talking" with this AP.

EDIT (I didn't see seth's post):

seth wrote:

Try reloading ath9k w/ nohwcrypt=1 (that's probably why lo1 asked for the running modules attributes)
Does the password contain non-ascii characters?

Exactly, also I still don't get if powersaving is actually enabled or disabled by default on ath9k (in doubt, throw it out of the window)

Last edited by lo1 (2018-01-23 22:05:05)

sharethewisdom · 2018-01-25 22:04:18

Thanks for the suggestions, the AP works fine for a Windows 10 PC. I do own the router... but I should get the admin panel passphrase from someone who is abroad at the moment. I don't think anyone changed the router's configuration though.

seth wrote:

Does the password contain non-ascii characters?

only printable ascii chars, no spaces

after turning nohwcrypt on, systool -avm ath9k returns:

Module = "ath9k"

  Attributes:
    coresize            = "155648"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "7D17CC093F34F0B0EFAE62D"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    blink               = "0"
    bt_ant_diversity    = "0"
    btcoex_enable       = "0"
    led_active_high     = "-1"
    nohwcrypt           = "1"
    ps_enable           = "0"

  Sections:
    .bss                = "0xffffffffc0cac9c0"
    .data               = "0xffffffffc0cac000"
    .exit.text          = "0xffffffffc0c9fd7d"
    .gnu.linkonce.this_module= "0xffffffffc0cac680"
    .init.text          = "0xffffffffc0cb2000"
    .note.gnu.build-id  = "0xffffffffc0ca0000"
    .orc_unwind         = "0xffffffffc0ca7888"
    .orc_unwind_ip      = "0xffffffffc0ca4fc0"
    .rodata.str1.1      = "0xffffffffc0ca4057"
    .rodata.str1.8      = "0xffffffffc0ca37b0"
    .rodata             = "0xffffffffc0ca0040"
    .smp_locks          = "0xffffffffc0ca4f18"
    .strtab             = "0xffffffffc0cb7db8"
    .symtab             = "0xffffffffc0cb3000"
    .text               = "0xffffffffc0c8b000"
    __bug_table         = "0xffffffffc0cac4d0"
    __mcount_loc        = "0xffffffffc0cab5b8"
    __param             = "0xffffffffc0cabd68"

lshw -class network

  *-network
       description: Wireless interface
       product: AR9285 Wireless Network Adapter (PCI-Express)
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 01
       serial: 48:5d:60:cb:6c:12
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath9k driverversion=4.14.13-1-ARCH firmware=N/A latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:e5600000-e560ffff

that's all I can do for today...

lo1 · 2018-01-26 10:52:05

If you really own the router, you can check for the reset button and hold it down with a pen/toothpick for ~15 seconds to trigger a factory reset (it sounds quite brutal, so let's say I'm telling you this just FYI).

Anyway, now that you disabled hwcrypt, how does the attempt to connect looks like?

wpa_supplicant -d -i wlp2s0 -c<(wpa_passphrase "yourssid" "yourpsk") #you can post it fully using pastebin clients

Not sure if useful, but I found this bug report which may be related. It seems that:
-802.11n may cause issues with this driver
-the AP can trigger a sort of port-security action, preventing any "unauthorized" device to connect. Which AP/router model is this?

Have a look at https://bugzilla.kernel.org/show_bug.cgi?id=14674 too.

sharethewisdom · 2018-01-27 13:45:08

here's the output of wpa_supplicant -d -i wlp2s0 -c<(...)

lo1 · 2018-01-27 15:52:02

No luck, either this is a firmware issue (try to connect to another AP before reporting this) or there's something wrong with your system (what if you try to boot and connect from the arch live USB/CD? do not chroot into your system in order for the test to make sense)

Arch Linux

#1 2018-01-23 09:17:07

wireless link not ready (4way_handshake_timeout)

#2 2018-01-23 10:08:13

Re: wireless link not ready (4way_handshake_timeout)

#3 2018-01-23 19:23:02

Re: wireless link not ready (4way_handshake_timeout)

#4 2018-01-23 21:47:20

Re: wireless link not ready (4way_handshake_timeout)

#5 2018-01-23 22:02:16

Re: wireless link not ready (4way_handshake_timeout)

#6 2018-01-25 22:04:18

Re: wireless link not ready (4way_handshake_timeout)

#7 2018-01-26 10:52:05

Re: wireless link not ready (4way_handshake_timeout)

#8 2018-01-27 13:45:08

Re: wireless link not ready (4way_handshake_timeout)

#9 2018-01-27 15:52:02

Re: wireless link not ready (4way_handshake_timeout)

Board footer