NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Lanopy's avatar
Lanopy
Follower
Aug 07, 2011

WNDAP350 - deauthenticated due to local deauth request

I have a WNDAP350 AP configed with WPA2-PSK. I am averaging about 40 clients in a high usage environment and and am experiencing random disconnects. I have both radios configured and the N network seems to remain stable. The 2.4 however will randomly disconnect users. The messages I am getting in the logs is "deauthenticated due to local deauth request. I have scanned for channel congestion etc and am having no luck isolating the issue. Any ideas on what I can look at to stabilize this?

2 Replies

  • grehund's avatar
    grehund
    Aspirant
    Oct 10, 2011
    I'm seeing the same log entries on a client's WNDAP350. I have updated to the latest firmware 2.0.27, and disabled WMM Powersave, as suggested by some other forum users. Neither of these changes have resolved the issue.

    My client would be lucky to have 5 simultaneous wireless users, yet we experience the same issues as you.

    I have tried changing to just 802.11a, changing to WPA1, even Open, the issue still prevails. :-(

    If you get this resolved, please post back. I will do the same.
  • RandolphBell's avatar
    RandolphBell
    Aspirant
    Oct 01, 2013
    This is clearly a memory leak in the current firmware. No matter what setting you use if you are streaming a considerable amount of bandwidth the system will eventually provide the following error messages

    Sep 30 19:53:11 hostapd: wifi0vap0: STA bc:c6:db:1b:26:xx IEEE 802.11: disassociated
    Sep 30 19:53:12 hostapd: wifi0vap0: STA bc:c6:db:1b:26:xx IEEE 802.11: associated
    Sep 30 19:53:15 hostapd: wifi0vap0: STA bc:c6:db:1b:26:xx IEEE 802.11: deauthenticated due to local deauth request
    Sep 30 19:53:15 hostapd: wifi0vap0: STA bc:c6:db:1b:26:xx IEEE 802.11: disassociated

    I've modified a number of settings to provide a somewhat reasonable configuration. I say somewhat in that I'm basing "working" on streaming an HD Netflix video and despite encountering this error message repeatedly the buffer in Netflix is able to mask the error. The configuration I settled on is
    as follows

    Channel / Freequency - Auto
    MCS Index / Data Rate - Best
    Channel Width - 40mhz
    Guard Interval - long 800ns
    Output Power - Full

    I challenge Netgear to respond to or resolve this issue.

    -Randy