Modify

Opened 4 years ago

Closed 4 years ago

Last modified 3 years ago

#14017 closed defect (fixed)

MLME-AUTHENTICATE/MLME-DELETEKEYS loop, can't connect to Wi-Fi

Reported by: katananja@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Trunk
Keywords: Cc:

Description

I don't know for how long i have to let the wireless up but after some time you can't make any wireless connection, it doesn't show any errors of any kind, it only shows a loop of this messages.

Fri Aug  9 21:44:00 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:44:00 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:44:00 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:45:32 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:45:32 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:45:32 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:46:26 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:46:26 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:46:26 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:46:49 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:46:49 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:46:49 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:46:53 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:46:53 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:46:53 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:47:17 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:47:17 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:47:17 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:47:55 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: authentication OK (open system)
Fri Aug  9 21:47:55 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-AUTHENTICATE.indication(00:00:00:00:00:00, OPEN_SYSTEM)
Fri Aug  9 21:47:55 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:49:01 2013 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: disassociated due to inactivity
Fri Aug  9 21:49:01 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DISASSOCIATE.indication(00:00:00:00:00:00, 4)
Fri Aug  9 21:49:01 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)
Fri Aug  9 21:49:02 2013 daemon.info hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Aug  9 21:49:02 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DEAUTHENTICATE.indication(00:00:00:00:00:00, 2)
Fri Aug  9 21:49:02 2013 daemon.none hostapd: wlan0: STA 00:00:00:00:00:00 MLME: MLME-DELETEKEYS.request(00:00:00:00:00:00)

When this happens I have to restar the interface with wifi down && wifi up command, but the defect it's intermitent.

 cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset
    Baseband Hang:  0
Baseband Watchdog:  0
   Fatal HW Error:  0
      TX HW error:  0
     TX Path Hang:  0
      PLL RX Hang:  0
        MCI Reset:  0

TP-Link TL-WR1043ND v1.8, r37745.
The test was done wiht a acer laptop and a Xperia ZL.

Attachments (1)

openwrt_r37751_wireless (5.3 KB) - added by katananja@… 4 years ago.
Wireshark compressed (gzip) dump file

Download all attachments as: .zip

Change History (10)

comment:1 Changed 4 years ago by katananja@…

Configuration file:

cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option channel '10'
	option hwmode '11ng'
	option path 'platform/ath9k'
	option htmode 'HT20'
	list ht_capab 'SHORT-GI-40'
	list ht_capab 'DSSS_CCK-40'
	option txpower '13'
	option country 'BR'
	option log_level '0'

config wifi-iface
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'Patocenter'
	option encryption 'psk2+ccmp'
	option macfilter 'allow'
	option key 'ERASED'
	list maclist 'ERASED'
	list maclist 'ERASED'
	list maclist 'ERASED'
	list maclist 'ERASED'
	list maclist 'ERASED'

Changed 4 years ago by katananja@…

Wireshark compressed (gzip) dump file

comment:2 Changed 4 years ago by katananja@…

Trunk r37751 still the same issue. I've attached a wireshark capture using linux and a TP-Link WN821N V3USB adapter.

Looks like a authentication issue (I've zeroed the info), don't know if it can't authenticate or if it doesn't want it to:

[299091.859738] wlan0: direct probe to 00:00:00:00:00:00 (try 1/3)
[299092.061421] wlan0: direct probe to 00:00:00:00:00:00 (try 2/3)
[299092.265154] wlan0: direct probe to 00:00:00:00:00:00 (try 3/3)
[299092.469177] wlan0: authentication with 00:00:00:00:00:00 timed out

My Xperia ZL shows the same problem with a different error, ctrl-event-assoc-reject status_code=1 it means nothing to pinpoint where exactly the error might be, but I hope to bring some light over this issue.

The last known trunk where this error doesn't/didn't happen was Trunk r37109.

Of course, the correct password is provided and the issue goes away if you restart the interface with wifi down && wifi up, this issue can came back after a few minutes or a few hours, I've verified a window of 28 minutes to 2 hours that this issue can occur.

I've attached a dump from Wireshark, it's gziped.

comment:3 Changed 4 years ago by katananja@…

Trunk r37804 and still the same issue, now the problem is when you start the interface with cron, as soon as you enable the wifi it stop responding exact the same way.

This is my cron settings

0	7	*	*	1-5	wifi up
0	8	*	*	1-5	wifi down
0	19	*	*	1-5	wifi up
59      23      *       *       1-5     wifi down
0	7	*	*	6-0	wifi up
59	23	*	*	6-0	wifi down

comment:4 Changed 4 years ago by katananja@…

Looks like the issue was solved, using trunk r37813 but I need a few more days to confirm.

comment:5 Changed 4 years ago by katananja@…

Using Trunk r37821, still some issues. Your device tries 7 to 10 times before it can authenticate.

comment:6 Changed 4 years ago by katananja@…

Using trunk r37821, looks like this issue it's fixed.

comment:7 Changed 4 years ago by katananja@…

Trunk r37854, it is fixed.

comment:8 Changed 4 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

comment:9 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.