Linksys EA8500 - Wifi Failure - Multiple Authentications

Installing and Using OpenWrt
1

Hey guys!
Some devices connected to my router is having some issues to keep wifi connected.

In system log I get tons of this message:

Tue Dec 5 19:04:14 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: authenticated
Tue Dec 5 19:04:14 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: associated (aid 2)
Tue Dec 5 19:04:17 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: authenticated
Tue Dec 5 19:04:17 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: associated (aid 2)
Tue Dec 5 19:04:20 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: authenticated
Tue Dec 5 19:04:20 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: associated (aid 2)
Tue Dec 5 19:04:28 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: deauthenticated due to local deauth request
Tue Dec 5 19:04:38 2017 daemon.info hostapd: wlan0: STA ec:17:2f:9d:92:5a WPA: group key handshake completed (RSN)
Tue Dec 5 19:05:21 2017 daemon.info hostapd: wlan1: STA 4c:66:41:24:dd:73 IEEE 802.11: authenticated
Tue Dec 5 19:05:21 2017 daemon.info hostapd: wlan1: STA 4c:66:41:24:dd:73 IEEE 802.11: associated (aid 4)
Tue Dec 5 19:05:24 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: authenticated
Tue Dec 5 19:05:24 2017 daemon.info hostapd: wlan0: STA 10:f0:05:6e:e0:60 IEEE 802.11: associated (aid 2)+

For example, in my Desktop I can barely connect to Wifi 2.4GHz, I get a message in Windows saying: Trying to connect (forever) until I go to the wifi properties and select " 5GHz Prefered" or "5GHz Only", but it stills take time to connect (but at least it connects after a while).

I've already tried to factory reset the device, but the problem still persists (and I have just upgraded to lastest LEDE version yesterday).

2

Sounds like a weak signal.

If channel selection is set to auto try using channel 1, 6, or 11 for 2.4 Ghz.

Make sure WMM is selected.

3

It can't be weak signal.
I'm just 10 meters from the router, and my Smartphone is getting almost full signal bars. And in the PC I can see strong signal.

Channel is manually set to 11 and WMM is already activated.

I've seem a really old topic in OpenWRT Forum but I don't think it applies here: https://dev.openwrt.org/ticket/10084
Probably already patched (6 years old, it must be).

Any other thoughts?

4

SSH into the router and run the following...

cat /etc/config/network

cat /etc/config/wireless

Make sure to obscure the "option key" value(s) in the wireless config results before posting.

5

cat /etc/config/network

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd0a:8e7d:8998::/48'

config interface 'lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option _orig_ifname 'eth0.1'
        option _orig_bridge 'true'
        option ifname 'eth0.1'
        option type 'bridge'

config device 'lan_dev'
        option name 'eth0.1'
        option macaddr '14:91:82:7f:20:19'

config device 'wan_dev'
        option name 'eth0.2'
        option macaddr '14:91:82:7f:20:19'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 2 3 4 0t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 0t'

config interface 'USB_TETHER'
        option proto 'dhcp'
        option ifname 'usb0'
        option peerdns '0'
        option dns '208.67.222.222 208.67.220.220'

cat /etc/config/wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option hwmode '11g'
        option path 'soc/1b500000.pci/pci0000:00/0000:00:00.0/0000:01:00.0'
        option country 'BR'
        option txpower '20'
        option disabled '0'
        option channel '11'
        option htmode 'HT40'

config wifi-device 'radio1'
        option type 'mac80211'
        option hwmode '11a'
        option path 'soc/1b700000.pci/pci0001:00/0001:00:00.0/0001:01:00.0'
        option htmode 'VHT80'
        option country 'BR'
        option txpower '24'
        option channel '112'

config wifi-iface
        option device 'radio1'
        option mode 'ap'
        option network 'lan'
        option encryption 'psk2'
        option key 'XXXXXXXXXXXXXXXXXXXXXXXX'
        option ssid 'House'

config wifi-iface
        option device 'radio0'
        option mode 'ap'
        option ssid 'House'
        option network 'lan'
        option encryption 'psk2'
        option key 'XXXXXXXXXXXXXXXXXXXXXXXX'

By the way, if I use different SSID for 2.4GHz and 5GHz, it stills drops the connection.

1 Like
6

can you run this command "iw list"from terminal, and paste it's output here.

7

iw list

Wiphy phy1
        max # scan SSIDs: 16
        max scan IEs length: 199 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0xf RX 0xf
        Configured Antennas: TX 0xf RX 0xf
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 2:
                Capabilities: 0x19ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-31
                VHT Capabilities (0x339b79b2):
                        Max MPDU length: 11454
                        Supported Channel Width: neither 160 nor 80+80
                        RX LDPC
                        short GI (80 MHz)
                        TX STBC
                        SU Beamformer
                        SU Beamformee
                        MU Beamformer
                        MU Beamformee
                        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
                Frequencies:
                        * 5180 MHz [36] (17.0 dBm)
                        * 5200 MHz [40] (17.0 dBm)
                        * 5220 MHz [44] (17.0 dBm)
                        * 5240 MHz [48] (17.0 dBm)
                        * 5260 MHz [52] (24.0 dBm) (radar detection)
                        * 5280 MHz [56] (24.0 dBm) (radar detection)
                        * 5300 MHz [60] (24.0 dBm) (radar detection)
                        * 5320 MHz [64] (24.0 dBm) (radar detection)
                        * 5500 MHz [100] (24.0 dBm) (radar detection)
                        * 5520 MHz [104] (24.0 dBm) (radar detection)
                        * 5540 MHz [108] (24.0 dBm) (radar detection)
                        * 5560 MHz [112] (24.0 dBm) (radar detection)
                        * 5580 MHz [116] (24.0 dBm) (radar detection)
                        * 5600 MHz [120] (24.0 dBm) (radar detection)
                        * 5620 MHz [124] (24.0 dBm) (radar detection)
                        * 5640 MHz [128] (24.0 dBm) (radar detection)
                        * 5660 MHz [132] (24.0 dBm) (radar detection)
                        * 5680 MHz [136] (24.0 dBm) (radar detection)
                        * 5700 MHz [140] (24.0 dBm) (radar detection)
                        * 5720 MHz [144] (24.0 dBm) (radar detection)
                        * 5745 MHz [149] (30.0 dBm)
                        * 5765 MHz [153] (30.0 dBm)
                        * 5785 MHz [157] (30.0 dBm)
                        * 5805 MHz [161] (30.0 dBm)
                        * 5825 MHz [165] (30.0 dBm)
                        * 5845 MHz [169] (disabled)
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports VHT-IBSS.
Wiphy phy0
        max # scan SSIDs: 16
        max scan IEs length: 209 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports AP-side u-APSD.
        Available Antennas: TX 0xf RX 0xf
        Configured Antennas: TX 0xf RX 0xf
        Supported interface modes:
                 * managed
                 * AP
                 * AP/VLAN
                 * monitor
                 * mesh point
        Band 1:
                Capabilities: 0x19ef
                        RX LDPC
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-31
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm)
                        * 2472 MHz [13] (20.0 dBm)
                        * 2484 MHz [14] (disabled)
        valid interface combinations:
                 * #{ managed } <= 1, #{ AP, mesh point } <= 16,
                   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }

        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports VHT-IBSS.
8

Anyone? +++

9

After associating, the client should participate in the WPA handshake. Then you get an "AP-STA-CONNECTED" and "WPA: pairwise key handshake completed" in the log. That is not happening with this particular client though it is apparently working with others.

This could be because Windows has the network stored with no encryption. First try forgetting the network and starting over.

Also move closer just to be absolutely sure it is not a weak signal.

You could also fall back to HT20 in case that is causing a problem with this client. HT40 in the 2 GHz band should only be considered when there are absolutely no neighboring wifi networks.

10

Weird...
This wifi failure is most happening with this Windows client, but sometimes it affects smartphones and smart tv as well.

I'm sure it's not weak signal because I'm really close to the router.
Talking about forgetting network, I've done that so many times. This Windows computer has 2 wifi adapter, built-in Intel (X370 Taichi) and another PCI-E TP-LINK T9E, this error happens for both. So I suppose it's more like to be a Windows problem than router, right?

It's weird because when I use my Samsung S7 Edge to "share" my wifi, I do not get this authentication problem. Basically my S7 Edge connects to my router wifi and then share using the hotspot function. When I do this way, everything works flawless.

When you say fall back to HT20, is this that 20Mhz/40Mhz stuff? If it is, I've already set to 20Mhz only in 2.4GHz radio via LUCI, and I still have that issue with this Windows machine :frowning: .

Thank you, I'll look for a solution for this Windows client.

11

I would also check for mismatched wireless security settings.

12

What do you mean?

13

Router wireless security settings -

Router

Wireless network adapter security settings -

Wireless Adapter

14

Both are using forced AES

15

What about encryption and key?

16

Same for both.
WPA2-Personal (windows)
WPA2-PSK (router)

Security Key, same for both.
I've just set auto channel for both 2.4GHz and 5GHz and it seems now I can connect easily... let's see if I will have dropped connection.

17

This is a nice tool (free but requires email registration) from Lizard Systems for analyzing wireless networks...

https://lizardsystems.com/wi-fi-scanner/

18

By the way, setting auto channel did not help :frowning:

IntelTP-LINK

19

On the Windows devices, open a Command prompt and run (one at a time)...

ipconfig /release

ipconfig /renew

20

Problem still persists after ipconfig... :frowning: