Wireless client can't connect - deauthenticated

[jkemenade]

Hi,

Am I running v1.8.0 on a TP-Link 1043ND v2 and most is running fine.
After a reboot of the router one wireless client can't connect to the router anymore. This is what logread says:
Sun Oct 11 21:37:56 2015 daemon.info hostapd: wlan0: STA 00:2647:7d:0f IEEE 802.11: authenticated
Sun Oct 11 21:37:56 2015 daemon.info hostapd: wlan0: STA 00:2647:7d:0f IEEE 802.11: associated (aid 4)
Sun Oct 11 21:38:04 2015 daemon.info hostapd: wlan0: STA 00:2647:7d:0f IEEE 802.11: deauthenticated due to local deauth request

WHY, it worked before the reboot and doesn't after. Can one of you help me investigate?

John

[jkemenade]

wireless is setup as WPA2 PSK with a 13-digit password

[nworbnhoj]

This is a known issue and is getting a lot of focus at the moment
viewtopic.php?f=14&t=7631&start=10#p32086

If you are using the Guest WiFi Network feature then I would suggest turning it off until the issues is resolved.

[jkemenade]

Thanks a lot for your reply.
I am indeed using the Guest network feature. However, turning it off does not solve the problem.

The strange thing is that only this wireless client has this strange problem (but not always to make it even stranger).

John

[nworbnhoj]

Yep - Guest network is not the root cause, but it made the difference in my case. Keep an eye on the forum for builds based on OpenWRT CC - usually by @ispyisail

[jkemenade]

Thanks man.

I have many wireless clients, but this deauthentication problem occurs for only one specific client

Code: Select all

Tue Oct 13 19:37:15 2015 daemon.info hostapd: wlan0: STA 00:26:ab:47:7d:0f IEEE 802.11: authenticated
Tue Oct 13 19:37:15 2015 daemon.info hostapd: wlan0: STA 00:26:ab:47:7d:0f IEEE 802.11: associated (aid 4)
Tue Oct 13 19:37:23 2015 daemon.info hostapd: wlan0: STA 00:26:ab:47:7d:0f IEEE 802.11: deauthenticated due to local deauth request

The deauth request is ALWAYS 8 seconds after the authentication.

John

[jkemenade]

Hmmm. Deauthentication occurs only on TP-Link 1043ND v2 running Gargoyle 1.8.0

All works fine on TP-Link 1043ND v1 running Gargoyle 1.8.0

Same network config

[FishHead]

I'm having very similar issues with my router. See this thread: http://www.gargoyle-router.com/phpbb/vi ... bef#p32227

[jkemenade]

Solved by upgrading to 1.9.0

[Volaris]

Solved by upgrading to 1.9.0

Yup. Should also be fixed in 1.8.1.

I had similar problems from 1.7 to 1.8. I found the problem was that by default it disabled ANI. Removing that line, as mentioned in the thread below, fixed wireless stability.
http://www.gargoyle-router.com/phpbb/vi ... 1&start=40

Gargoyle's builders then implemented the fix in 1.8.1 and 1.9, so those two firmwares (and anything released after them from here on) should be stable if this was the cause to your problem. The fix isn't specific to a router... might help other routers if they had similar issue. (was related to some AR71XX routers according to OpenWRT).