NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
dolphin74
Feb 14, 2013Follower
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,...
RandolphBell
Oct 01, 2013Aspirant
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
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