Modify

Opened 8 years ago

Closed 7 years ago

#7413 closed defect (duplicate)

DIR-825: "Deauthenticated due to local deauth request" with all latest snapshots.

Reported by: anonymous Owned by: developers
Priority: response-needed Milestone: Backfire 10.03.1
Component: base system Version: Trunk
Keywords: Cc:

Description

Using all latest trunk releases (own compiled or precompiled snapshots) on DIR-825b1 cause "deauthenticated due to local deauth request" errors in log. Ofcourse due to this problem all other wlan gear I own cannot authenticate (WPA2/AES) and connect. I have to restart both router and clients a few times before being able to connect. Even then, when a client disconnects due to inactivity or power-down, it cannot reconnect and Openwrt fills log with the above message.

BTW, Backfire 10.03 and the first snapshots released since then didn't had this problem. If first appeared on May 23th snapshop and still exists on the latest one.

Attachments (2)

systemlog_hostapd-error.txt (15.9 KB) - added by anonymous 8 years ago.
hostapd debug log on g300nh
WNDR3700 WPA2 Errorlog and etconfignetwork dump.txt (8.9 KB) - added by Goofball <goofball222@…> 7 years ago.
Error Log from WNDR3700 and /etc/config/wireless dump

Download all attachments as: .zip

Change History (38)

comment:1 Changed 8 years ago by SakisP

I confirm this issue. As reporter said, it never happened before the later trunk releases.

BTW I've noticed that this wireless authentication problem only occurs when using wlan1 (5Ghz). With 2.4GHz radio seems working ok.

comment:2 Changed 8 years ago by anonymous

@SakisP: I've seen that happening when using wlan0 too, thought it's rare compared to 5Ghz.

comment:3 follow-up: Changed 8 years ago by anonymous

Just checked my logs and found that at relatively old r21096 on 5Ghz wlan this message appears too.
At this revision it looks like wifi clients are trying to connect several times, and after 2-4 failures with "deauthenticated due to local deauth request" message, they finally are able to successfully connect.

comment:4 in reply to: ↑ 3 Changed 8 years ago by Athan

Replying to anonymous:

At this revision it looks like wifi clients are trying to connect several times, and after 2-4 failures with "deauthenticated due to local deauth request" message, they finally are able to successfully connect.

Unfortunately seems that in latest trunk, 5Ghz clients are not able to successfully connect even after dozens of "deauthenticated due to local deauth request" errors.
On 2.4Ghz things are much betterm although such errors still appear in log every while.

comment:5 Changed 8 years ago by anonymous

I've spent a dozen hours investigating this issue with no success.
I tried wpa-mini, hostapd, with AES & TKIP configured clients but Openwrt always denies 5GHz connections emitting the "Deauthenticated due to local deauth request" error message.

I don't know guys what you've changed in recent trunk releases, but it turned 5GHz radio completely useless. Older trunk snapshots, as well as backfire 10.03 worked fine, though...

comment:6 Changed 8 years ago by anonymous

I noticed exactly this same problem on my WNDR3700.

I'm using two Linksys WET610N bridges and cannot connect anymore to my WNDR3700, on any band (2.4 and 5GHZ). Also, openwrt log is filled with "Deauthenticated due to local deauth request" error messages.

Before the latest 2-3 trunk releases everything worked fine with no traces of this issue. Seems that something addeed recently broke the whole ar7161 platform.

comment:7 Changed 8 years ago by anonymous

I can confirm this behaviour also in buffalo wzr-hp-g300nh running backfire 10.03 wpa2. clients are running vista and xp. Attached is system log with hostapd debug enabled.

Changed 8 years ago by anonymous

hostapd debug log on g300nh

comment:8 Changed 8 years ago by anonymous

Confirmed on a WNDR37000, after a while clients disconnect (and cannot reconnect) and this is what it says in the logs.

comment:9 Changed 8 years ago by dirtyfreebooter <openwrt@…>

I can confirm similar behavior on DIR-825 running trunk on both 2.4GHz and 5.0GHz using WPA2 + AES. The client machine is a June 2009 Macbook Pro connecting to N band on 2.4 GHz and 5 GHz frequencies.

From the logs...

Jun 25 13:11:35 router daemon.info hostapd: wlan0: STA 68:7f:74:12:b0:18 WPA: group key handshake completed (RSN)
Jun 25 13:11:35 router daemon.info hostapd: wlan0: STA 00:14:51:ef:b2:e6 WPA: group key handshake completed (RSN)
Jun 25 13:11:35 router daemon.info hostapd: wlan0: STA 00:21:e9:1b:cc:5d WPA: group key handshake completed (RSN)
Jun 25 13:11:35 router daemon.info hostapd: wlan0: STA 00:26:08:dd:ba:89 WPA: group key handshake completed (RSN)
Jun 25 13:11:35 router daemon.info hostapd: wlan0: STA 00:26:08:dd:ba:89 WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
...
Jun 25 13:21:35 router daemon.info hostapd: wlan0: STA 68:7f:74:12:b0:18 WPA: group key handshake completed (RSN)
Jun 25 13:21:35 router daemon.info hostapd: wlan0: STA 00:14:51:ef:b2:e6 WPA: group key handshake completed (RSN)
Jun 25 13:21:35 router daemon.info hostapd: wlan0: STA 00:21:e9:1b:cc:5d WPA: group key handshake completed (RSN)
Jun 25 13:21:38 router daemon.info hostapd: wlan0: STA 00:26:08:dd:ba:89 IEEE 802.11: deauthenticated due to local deauth request

The newer Macbook Pro always has those "unexpected replay counter" messages. The other MAC addresses in there are from a first generation Intel Macbook Pro (32-bit Core Duo, 802.11g only), iPhone 3G, Linksys WRT610Nv2 as a client bridge. Those clients never see the replay count message and never get unexpectedly disconnected. Is there a relation there? I am not sure, but it looks that way (at least initially).

comment:10 Changed 8 years ago by nbd

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

Please try a newer version with my latest fixes.
Additionally, this is a duplicate of #6667

comment:11 Changed 8 years ago by dirtyfreebooter <openwrt@…>

Yea, I can confirm now with over 24 hrs using trunk build r22048, I have not had one single strange disconnect. Before this was happening every 15-30 mins, constantly. I am pretty sure this bug is fixed :-) Thanks so much. I was just waiting to run for at least 24 hrs before reporting. I'll use #6667 in the future if this issue arises again.

comment:12 Changed 7 years ago by samuelpward@…

  • Resolution duplicate deleted
  • Status changed from closed to reopened

i am still having this issue. i only have one of the aerials turned on running at 2.4GHz and its happening about twice a day. im using a DLINK DIR-825 also and im running Backfire (r22556).

comment:13 Changed 7 years ago by nico

  • Priority changed from highest to response-needed

Can you confirm this issue is still present in 10.03.1-rc1 ?

comment:14 Changed 7 years ago by anonymous

sorry i thought i had been using that. i will reflash it now with rc1 and test.

comment:15 Changed 7 years ago by samuelpward@…

it is still doing it after i reflashed the dlink dir-825 with rc1, i was using rc1 before aswell. any other information that i could supply please just ask.

comment:16 Changed 7 years ago by samuelpward@…

i read the link to ticket #6667 and followed one of the posts that said it worked after disabling wireless n. i have done the same and just running the 2.4GHz aerial on g and i have had no disconnects.

comment:17 Changed 7 years ago by anonymous

Just upgraded to Backfire 10.03.1-rc1 from Kamikaze, I can also confirm the problem still happens for the DIR-825 Rev.B2.
Same experience as for samuelpward, the disconnects happen on an aerial with N enabled.
In my case the device getting disconnects is a WET610N.
The devices using G have no issues.

comment:18 Changed 7 years ago by anonymous

I'm on the trunk build downloaded 14th August and I can confirm seeing this on my DIR-825 B2 EU. (2.4GHz band)

comment:19 Changed 7 years ago by lucaferr

DIR-825 B2 EU, same problem, build r22871.

comment:20 Changed 7 years ago by anonymous

I'm using 10.03.1-rc3 with a Buffalo WZR-HP-G300NH and am experiencing this issue as well. After several hours of working normally, wireless clients get disconnected and can no longer connect. I have many of the same error messages in the system log ("deauthenticated due to local deauth request"),

Using WPA2-PSK and all clients configured to use AES encryption.

comment:21 Changed 7 years ago by anonymous

In message above forgot to specify I am indeed using wireless N.

comment:22 Changed 7 years ago by anonymous

DIR-825 B1, same problem on backfire-rc3 and trunk r23080.

Would be happy to help debug. Are there any instructions
anywhere? Thanks.

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

Please try r23097

comment:24 in reply to: ↑ 23 Changed 7 years ago by anonymous

Replying to nbd:

Please try r23097

Hi nbd... looking hopeful so far, will report back after some more testing either way.

comment:25 Changed 7 years ago by nbd

Added a fix for another warning related to this in r23100

Please include that in your tests as well.

comment:26 Changed 7 years ago by anonymous

nbd, running with r23106 here, and at the very least the situation is much
improved. Will watch it closely over next couple of days. It's exciting to
think that i can finally use Openwrt instead of DD. Thanks for the great
work!

comment:27 Changed 7 years ago by nbd

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

According to several reports, this issue is fully fixed now.

comment:28 Changed 7 years ago by anonymous

anyone can compile a trunk r23106 for bcm63xx/rg100a?

comment:29 Changed 7 years ago by Anton Shapiro <antshforums@…>

  • Resolution fixed deleted
  • Status changed from closed to reopened

Unfortunately, I just compiled today's latest trunk, and am seeing these exact errors in my system log. I am using a WNDR3700. This happens with all my clients (all using 802.11n, 2 on the 2.4 radio and 2 on the 5GHz radio). The 5GHz clients use Mikrotik R52N (AR9220) Mini-PCI cards and windows XP SP3. The same errors are reported when my iPad and iPhone 4 connect to the 2.4 band. If there is any other information I could provide to help out, please let me know.

comment:30 Changed 7 years ago by Anton Shapiro <antshforums@…>

BTW, I am running with 2 SSID's on the 2.4 band and one on the 5GHz band, all three using WPA2-PSK

comment:31 Changed 7 years ago by ziesemer

Things have improved after r23106, etc., but even after a recent branch build of backfire (r23987), there still appear to be too many issues to use this for normal use. (I have a DIR-825 B1, and have tested both the 2.4 and 5GHz bands, using WPA+WPA2 combo.) In running continual pings from a wireless laptop to the router itself, most responses are 1-3 ms, but about every 5 pings hits somewhere between 800-1200ms, and sometimes worse. I also continue to experience the same errors in the system log as mentioned above.

Same as Anton, if there is any other information we can provide to help out, please let us know. Thanks!

comment:32 Changed 7 years ago by ziesemer

I also failed to mention the packet loss:

918 packets transmitted, 473 packets received, 48.5% packet loss
round-trip (ms)  min/avg/max/med = 1/106/1770/2

(More text to bypass the spam filter: I realize that the ping packet loss isn't the root of the problem, but may help demonstrate the impact of this issue.)

comment:33 follow-up: Changed 7 years ago by Glenno <glenno@…>

It is definitely getting better (Trunk r24037), the only device I cant keep reliably connected to WiFi is my Chumby Classic. I think it uses the RT71 WiFi driver. Up until a build around r23500 it would disconnect every 10 minutes on the dot. Now it still disconnects randomly, but it reconnects automatically after some random time (from seconds to minutes).

The Chumby worked fine with the stock DIR-825 firmware.

Kudos to the Ath9k team though, its working pretty dammm well at the moment.

comment:34 in reply to: ↑ 33 Changed 7 years ago by agb

Replying to Glenno <glenno@…>:

It is definitely getting better (Trunk r24037), the only device I cant keep reliably connected to WiFi is my Chumby Classic. I think it uses the RT71 WiFi driver. Up until a build around r23500 it would disconnect every 10 minutes on the dot. Now it still disconnects randomly, but it reconnects automatically after some random time (from seconds to minutes).

The Chumby worked fine with the stock DIR-825 firmware.

Kudos to the Ath9k team though, its working pretty dammm well at the moment.

FWIW, my Chumby doesn't like a number of wireless APs, including the stock firmware on some atheros based single-stream N devices. Chumby related issues are not exclusive to ath9k.

Changed 7 years ago by Goofball <goofball222@…>

Error Log from WNDR3700 and /etc/config/wireless dump

comment:35 Changed 7 years ago by Goofball <goofball222@…>

I am seeing this as well on a WNDR3700 running both Backfire 10.03.1-rc4 and Trunk r24246. I have a TiVo G adapter and Wii that both appear to be fine.

This EAPOL error happens with my Blackberry 8530. It works up until it sits overnight or for any other extended period and eventually disconnects requiring a hard boot of the device to re-establish the connection.

My laptop Intel 4956AG card also appears to have instances of the EAPOL error but it doesn't appear to be affecting connectivity yet. This might just be because I normally only have the laptop powered on when it is in use. I'll plug it in and leave it running overnight tonight to check results.

I've attached a dump of my /etc/config/wireless and a logread grep for wlan0 which is the only interface I have devices attached to right now.

comment:36 Changed 7 years ago by nbd

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

Stability issues tracked in #8830

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.