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

Forum Discussion

dolphin74's avatar
dolphin74
Follower
Feb 14, 2013

WNDAP350 + last firmware + deauth wireless bridge

Kind all,

I have 4 WNDAP350 covering a big area. Both the antenna (integrated) are functionally (2.4 & 5.4) and I bridged in 2 separate p2p bridge via 2,4GHz antenna.
So I have 2 AP fixed channel, 20MHz width in one place, anda other 2 fixed channel, 20 MHz width in another place.

After a while, APs bridged disconnect from the respective master. So I need to rebbot the AP, and for a while everything running good. About 2-3 station for each place.

WPA2 only for all the security policy (bridged and access).

Does anyone has suggestions for working with this kind of configuration (very easy IMHO)?

Inside the log the message is always the same when we lost conectivity with the bridged AP..

"Feb 13 18:24:28 hostapd: wifi0wds0: STA e0:91:f5:c5:f1:40 IEEE 802.11: associated
Feb 13 18:24:30 hostapd: wifi0wds0: STA e0:91:f5:c5:f1:40 IEEE 802.11: deauthenticated due to local deauth request
Feb 13 18:24:30 hostapd: wifi0wds0: STA e0:91:f5:c5:f1:40 IEEE 802.11: associated
Feb 13 18:24:31 hostapd: wifi0wds0: STA e0:91:f5:c5:f1:40 WPA: received EAPOL-Key 2/4 Pairwise with unexpected replay counter
Feb 13 18:24:31 hostapd: wifi0wds0: STA e0:91:f5:c5:f1:40 WPA: pairwise key handshake completed (RSN)"

Any help is very appreciate. Thanks! :)

2 Replies

  • 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
  • Randy,

    What firmware are you using these settings on? I've had nothing but problems with this AP, especially with Apple products.