Linksys EA8500 - Wifi Failure - Multiple Authentications

If it were my router, I would reflash and reconfigure...

Reflaxed and reconfigured.
Everything is back normal :smiley:

Thank you buddy.

Following this thread, I would really like to know any thoughts on what the reflash may have done to resolve connectivity with a single client. I can understand perhaps resolving some sort of corruption, but from the thread, everything seems fine except for this one client.

What are the transient / variable parts of the image that could be cleared or re-written to impact a single client? i.e. what did the re-flash do to resolve this one client issue.

I have seen this type of client behaviour in logs before and recently experienced some similar/strange connectivity issues after upgrading my EA8500 to 17.01.4 which I did not dive into after restoring connectivity for my tasks at hand.

It really sounds like there was an issue in the build here with an unknown root cause that is going to pop up again.

I think it's a bug as well, as soon as I received this router I just installed LEDE (I didn't even play around with the stock firmware). So I set everything the way I wanted and everything worked fine for a couple months. Then I was having trouble with specific wifi clients and I had to factory reset the router and set up everything again.

But, since no one reported this as an issue, I thought that maybe it's a problem on my side (bad config / corrupted data).

I hope someone can figure it out what kind of bug is this, so I don't have to reflash every once in a while.

This seems like congestion on the channel near the client.

Are you able to increase power of the AP?

It can't be congestion. I was the only person in my neighborhood to have Wifi (lol).
Now everything is working again.

I've seen similar things happen with other firmware, so it's not isolated to LEDE...

Do you know if this occurs to the stock firmware?

OK.... I think it was too soon to say it was fixed.
Well... actually it was fixed, for one client. Now I'm still having this issue with another client when it tries to stream local content over wifi (using BubbleUPnP). This specific client is running Android 7 (Samsung Galaxy S6) and after some minutes it gets disconnected and interrupts its stream. Should we consider this a bug? If so, where should I report it to get more visibility and may have this fixed in future builds? The log follows below.
*BTW: The client reports STRONG WIFI SIGNAL, 75 Mbps.

Wed Dec 13 21:07:52 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:07:52 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA 84:9c:a6:cb:3d:9a WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA a4:2b:b0:e2:d0:59 WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA ec:17:2f:9d:92:5a WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA 4c:09:d4:5e:09:ee WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA 78:44:76:a4:27:c0 WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:49 2017 daemon.info hostapd: wlan0: STA c4:43:8f:5d:5c:90 WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:50 2017 daemon.info hostapd: wlan0: STA 4c:66:41:24:dd:73 WPA: group key handshake completed (RSN)
Wed Dec 13 21:09:50 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:09:50 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:09:50 2017 daemon.info hostapd: wlan0: STA 00:ae:fa:50:0e:b4 WPA: group key handshake completed (RSN)
Wed Dec 13 21:10:08 2017 daemon.info odhcpd[483]: Using a RA lifetime of 0 seconds on br-lan
Wed Dec 13 21:11:41 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:11:41 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:13:42 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:13:42 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:15:49 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:15:49 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:17:46 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:17:46 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:18:28 2017 daemon.info odhcpd[483]: Using a RA lifetime of 0 seconds on br-lan
Wed Dec 13 21:19:41 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:19:41 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA 84:9c:a6:cb:3d:9a WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA a4:2b:b0:e2:d0:59 WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA ec:17:2f:9d:92:5a WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA 78:44:76:a4:27:c0 WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA 4c:09:d4:5e:09:ee WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA c4:43:8f:5d:5c:90 WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA 4c:66:41:24:dd:73 WPA: group key handshake completed (RSN)
Wed Dec 13 21:19:49 2017 daemon.info hostapd: wlan0: STA 00:ae:fa:50:0e:b4 WPA: group key handshake completed (RSN)
Wed Dec 13 21:21:37 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:21:37 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:22:38 2017 daemon.info odhcpd[483]: Using a RA lifetime of 0 seconds on br-lan
Wed Dec 13 21:22:55 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 IEEE 802.11: disconnected due to excessive missing ACKs
Wed Dec 13 21:22:55 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED fc:db:b3:58:f9:66
Wed Dec 13 21:23:25 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Wed Dec 13 21:23:33 2017 daemon.info hostapd: wlan1: STA fc:db:b3:58:f9:66 IEEE 802.11: authenticated
Wed Dec 13 21:23:33 2017 daemon.info hostapd: wlan1: STA fc:db:b3:58:f9:66 IEEE 802.11: associated (aid 1)
Wed Dec 13 21:23:33 2017 daemon.notice hostapd: wlan1: AP-STA-CONNECTED fc:db:b3:58:f9:66
Wed Dec 13 21:23:33 2017 daemon.info hostapd: wlan1: STA fc:db:b3:58:f9:66 WPA: pairwise key handshake completed (RSN)
Wed Dec 13 21:23:33 2017 daemon.info dnsmasq-dhcp[1084]: DHCPDISCOVER(br-lan) fc:db:b3:58:f9:66 
Wed Dec 13 21:23:33 2017 daemon.info dnsmasq-dhcp[1084]: DHCPOFFER(br-lan) 192.168.1.165 fc:db:b3:58:f9:66 
Wed Dec 13 21:23:33 2017 daemon.info dnsmasq-dhcp[1084]: DHCPREQUEST(br-lan) 192.168.1.165 fc:db:b3:58:f9:66 
Wed Dec 13 21:23:33 2017 daemon.info dnsmasq-dhcp[1084]: DHCPACK(br-lan) 192.168.1.165 fc:db:b3:58:f9:66 Galaxy-S6-Denis
Wed Dec 13 21:23:34 2017 daemon.info odhcpd[483]: Using a RA lifetime of 0 seconds on br-lan
Wed Dec 13 21:23:38 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:23:38 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128 
Wed Dec 13 21:23:43 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 IEEE 802.11: authenticated
Wed Dec 13 21:23:43 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 IEEE 802.11: associated (aid 8)
Wed Dec 13 21:23:43 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED fc:db:b3:58:f9:66
Wed Dec 13 21:23:43 2017 daemon.info hostapd: wlan0: STA fc:db:b3:58:f9:66 WPA: pairwise key handshake completed (RSN)
Wed Dec 13 21:23:44 2017 daemon.info dnsmasq-dhcp[1084]: DHCPREQUEST(br-lan) 192.168.1.165 fc:db:b3:58:f9:66 
Wed Dec 13 21:23:44 2017 daemon.info dnsmasq-dhcp[1084]: DHCPACK(br-lan) 192.168.1.165 fc:db:b3:58:f9:66 Galaxy-S6-Denis
Wed Dec 13 21:25:37 2017 daemon.notice odhcpd[483]: Got DHCPv6 request
Wed Dec 13 21:25:37 2017 daemon.warn odhcpd[483]: DHCPV6 SOLICIT IA_NA from 000300014c09d45e09ee on br-lan: ok fd68:b000:e930::c6b/128

You might check to see if you are running the current version of BubbleUPnP...

https://www.bubblesoftapps.com/bubbleupnpserver/#troubleshooting_startup

It's not necessary to run BubbleUPnP server.
It occurs local transconding (direct from the device).