Modify

Opened 7 years ago

Closed 7 years ago

Last modified 4 years ago

#7929 closed defect (duplicate)

hostapd rapid 'deauthenticated due to inactivity' disconnects using r23042

Reported by: dirtyfreebooter <openwrt-devel@…> Owned by: nbd
Priority: normal Milestone: Barrier Breaker 14.07
Component: packages Version: Trunk
Keywords: hostapd, disassociated, deauthenticated, inactivity Cc:

Description

Using a fresh build from today, r23042, I am seeing hostapd going crazy with *deauthenticated due to inactivity* messages. They seem to be only happening right now to one host on my network, a Linksys WRT610Nv2 router in client bridge mode. The router is running *cough* DD-WRT, but its a older build that I have been running for months without problem with OpenWrt, so I don't suspect its DD-WRT problem, as of right now.

I would note, when it happens, the wireless connection goes out and doesn't come back until the last authentication in the series completes.

Here is some log output:

Sep 12 19:47:18 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: authenticated
Sep 12 19:47:18 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: associated (aid 1)
Sep 12 19:47:18 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 WPA: pairwise key handshake completed (RSN)
Sep 12 19:52:57 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: authenticated
Sep 12 19:52:57 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: associated (aid 1)
Sep 12 19:52:57 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 WPA: pairwise key handshake completed (RSN)
Sep 12 19:52:57 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: disassociated
Sep 12 19:52:58 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: deauthenticated due to inactivity
Sep 12 19:53:00 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: authenticated
Sep 12 19:53:00 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: associated (aid 1)
Sep 12 19:53:00 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 WPA: pairwise key handshake completed (RSN)
Sep 12 19:53:01 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: disassociated
Sep 12 19:53:02 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: deauthenticated due to inactivity
Sep 12 19:53:02 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: authenticated
Sep 12 19:53:02 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 IEEE 802.11: associated (aid 1)
Sep 12 19:53:02 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 WPA: pairwise key handshake completed (RSN)
Sep 12 19:55:53 router daemon.info hostapd: wlan0: STA 7c:c5:37:3d:2c:6c IEEE 802.11: authenticated
Sep 12 19:55:53 router daemon.info hostapd: wlan0: STA 7c:c5:37:3d:2c:6c IEEE 802.11: associated (aid 1)
Sep 12 19:55:53 router daemon.info hostapd: wlan0: STA 7c:c5:37:3d:2c:6c WPA: pairwise key handshake completed (RSN)
Sep 12 19:57:10 router daemon.info hostapd: wlan0: STA 7c:c5:37:3d:2c:6c WPA: group key handshake completed (RSN)
Sep 12 19:57:10 router daemon.info hostapd: wlan0: STA 7c:c5:37:3d:2c:6c WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
Sep 12 19:57:15 router daemon.info hostapd: wlan1: STA 68:7f:74:12:b0:19 WPA: group key handshake completed (RSN)

If I can do any debugging, I will. Just let me know what you (nbd) want me to log ;-)

Attachments (0)

Change History (12)

comment:1 Changed 7 years ago by buildster

Pumping "one bit of kernel" (5 to 7) may help...

A brcm47xx box running on r23097 (linux 2.26.34.5) and b43 drivers spits out 3 types of hostapd messages: (1) rapid repeated "deauthenticated due to local deauth request"; (2) every ~30 seconds, "authenticated, associated (aid 1), airwise key handshake completed (RSN)"; (3) every 10 minutes, "group key handshake completed (RSN)". The WiFi connection was sluggish.

I just tried kernel 2.26.34.7 because of its several net related fixes. The (1) "deauthenticated" message has NOT shown in last ~24 hours. Still gets a bout of (2) once in 3~4 hours. And, every 10 minutes, the normal (3) "completed" message. The WiFi connection has been smooth, although not as fast as the old 2.4 wl.

comment:2 Changed 7 years ago by isleman

@dirtyfreebooter

as you can see there are no DHCP messages so the router may think that the other peer has gone off (no DHCP discover/request).
I tried to reboot the 802.11n router (BulletM2) getting a fresh dnsmasq and hostapd/wlan0.monitor session: the client associate with it successfully, I could see DHCP messages in logread output.
Then I tried to reboot the client and repeat the association: failed with the above messages 'deauthenticated due to inactivity', I could not see DHCP traffic.
It seems that a previous DHCP session is not repeated for the same machine... can you try there my test (reboot the router)?

just my two cents


comment:3 Changed 7 years ago by isleman

...still no reply.
Maybe this ticked is malformed, i.e. I think milestone kaey should be changed as 'Backfire 10.3' and not kamikaze.

I hope someone could change it at least to have a chance to get a reply (the ticket is still open from weeks ...)

comment:4 Changed 7 years ago by jow

  • Owner changed from developers to nbd
  • Status changed from new to assigned

comment:5 follow-up: Changed 7 years ago by nbd

Stability should be much better as of r24962 (backfire), r24954 (trunk). Please test again.

comment:6 in reply to: ↑ 5 Changed 7 years ago by anonymous

Replying to nbd:

Stability should be much better as of r24962 (backfire), r24954 (trunk). Please test again.

thank you!
I'll test backfire branch ASAP and I'll keep you posted.

isleman

comment:7 Changed 7 years ago by isleman

odd... I can associate with the node and get a lease and it seems pretty stable. But I cant wirelessy ping and reach the node pointing the default route IP received in the lease (i.e. the wlan1 IP address). No firewall rule is issued.

comment:8 Changed 7 years ago by isleman

Sorry to say, but same results building backfire r24999:
I'm able to associate with the router
I get a lease (101.159.115.89) from the router (101.159.115.1)
but I cant wirelessy reach the router (ping 101.159.115.1 fails)

comment:9 Changed 7 years ago by isleman

Below are the last lines from dmesg in my PC:

[ 1740.316073] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1740.332258] ===>rtllib_associate_procedure_wq(), chan:5
[ 1740.332264] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 1740.344247] rtl8192_SetWirelessMode(), wireless_mode:10, bEnableHT = 1
[ 1740.347613] Associated successfully
[ 1740.347617] normal associate
[ 1740.347630] Using G rates:108
[ 1740.347633] Successfully associated, ht enabled
[ 1740.347638] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 1740.357613] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1796.896254] ====>to send ADDBAREQ!!!!!
[ 1804.916248] ====>to send ADDBAREQ!!!!!
[ 1858.790607] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 1858.790699] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1860.310037] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1978.791233] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 1978.791312] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1980.310250] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 1981.852088] ====>to send ADDBAREQ!!!!!
[ 1989.852240] ====>to send ADDBAREQ!!!!!
[ 1990.852243] ====>to send ADDBAREQ!!!!!
[ 2098.789054] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 2098.789144] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 2100.310265] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 2218.791030] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 2218.791111] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 2220.310262] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 2338.790676] LPS leave: notify AP we are awaked ++++++++++ SendNullFunctionData
[ 2338.790753] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 2340.310278] ===>rtl8192se_link_change():ieee->iw_mode is 2

it seems forced to work in 40MHz cahnnel bandwidth mode:

[ 1740.332258] ===>rtllib_associate_procedure_wq(), chan:5
[ 1740.332264] HTSetConnectBwMode():pHTInfo->bCurBW40MHz:0
[ 1740.344247] rtl8192_SetWirelessMode(), wireless_mode:10, bEnableHT = 1

These are lines from dmesg while ping the AP files:

[ 3178.788349] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 3180.318279] ===>rtl8192se_link_change():ieee->iw_mode is 2
[ 3251.344900] ====>to send ADDBAREQ!!!!!
[ 3252.364541] ====>to send ADDBAREQ!!!!!
[ 3253.364243] ====>to send ADDBAREQ!!!!!
[ 3254.380260] ====>to send ADDBAREQ!!!!!
[ 3255.384043] ====>to send ADDBAREQ!!!!!
[ 3256.380237] ====>to send ADDBAREQ!!!!!
[ 3290.504025] ====>to send ADDBAREQ!!!!!
[ 3291.504241] ====>to send ADDBAREQ!!!!!
[ 3292.504301] ====>to send ADDBAREQ!!!!!
[ 3293.524180] ====>to send ADDBAREQ!!!!!
[ 3294.524244] ====>to send ADDBAREQ!!!!!
[ 3295.524028] ====>to send ADDBAREQ!!!!!

Hope it could help. Feel free to ask me for other tests.

comment:10 Changed 7 years ago by isleman

I apologize for the flood, I'm just trying to help to fix the problem...
I looked at the arp table of my pc: as soon as the association is completed it has the (right) MAC address and the (right) iface in order to reach the AP. Well, so I start to ping the AP but w/out success and looking at wireshark it says that my pc can't resolve the AP IP address (i.e. arping the AP fails).
In the meantime, network-manager in my pc (ubuntu 10.04) t does not report any disconnection...

comment:11 Changed 7 years ago by nbd

  • Resolution set to duplicate
  • Status changed from assigned to closed

ath9k stability issues are tracked in #8830, please try the latest version to see if it helps, and report your findings in that ticket.

If you have deauth/disassoc issues with b43, please open up a separate ticket to avoid introducing more driver confusion here.

comment:12 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.