NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bramschats1
Apr 22, 2011Aspirant
[WNAP210] fail to access after a while
Hello,
I have a WNAP210 access point and it is working very well, except for one strange thing.
I usually have 1 or 2 clients connected to the access point but every three weeks i have to reboot the access point because the client cannot connect to the WNAP210. After reboot everything works well again but after a few weeks it has to reboot again.
What can cause this issue?
Hope someone can help me on this issue.
I have a WNAP210 access point and it is working very well, except for one strange thing.
I usually have 1 or 2 clients connected to the access point but every three weeks i have to reboot the access point because the client cannot connect to the WNAP210. After reboot everything works well again but after a few weeks it has to reboot again.
What can cause this issue?
Hope someone can help me on this issue.
18 Replies
- rilexAspirantCan you access it via the admin page? If so, what do the logs say, if anything?
FWIW, my WNAP210 running the .12 firmware currently has an uptime of 23 days, but it has been up for longer. - bramschats1AspirantRilex,
Thanks for the reply,
here are the logs from before restarting:Apr 22 07:25:50 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
Apr 22 07:25:57 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
Apr 22 07:26:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
Apr 22 07:26:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
Apr 22 07:26:12 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
Apr 22 07:26:15 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
I don't know what the deauthenticated due to local deauth means, maybe you can help me.
I am running firmware:WNAP210_2.0.12
Is it possible to periodically restart the access point so i don't have to do this manually?
Hope you can help me.
thnx in advance. - rclarkTutor
bramschats wrote: Rilex,
Thanks for the reply,
here are the logs from before restarting:Apr 22 07:25:50 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
Apr 22 07:25:57 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
Apr 22 07:26:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
Apr 22 07:26:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
Apr 22 07:26:12 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
Apr 22 07:26:15 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
I don't know what the deauthenticated due to local deauth means, maybe you can help me.
I am running firmware:WNAP210_2.0.12
Is it possible to periodically restart the access point so i don't have to do this manually?
Hope you can help me.
thnx in advance.
I am experiencing this exact issue with one of my customers. It seemed to work better for awhile by restricting the channel use to 20 MHz, but now they're starting to experience the same issue - restarting the AP works sometimes, but not always. There's only 2-3 wireless devices (iPad's and iPhones).
-Randy - rilexAspirantI also restrict my AP to 20Mhz as 20/40 dynamic causes a Roku I have to randomly disconnect.
- bramschats1AspirantI took a look at my setup but it is already on 20MHz fixed.....!
- NerdyMikeAspirantI'm having an identical problem on multiple sites. For over a month I've been troubleshooting this with Netgear support. We've done all the basics including base station location, wiring, power supply and the unit itself. We've done factory resets and changed the location of the units. We've confirmed that the problem isn't any specific client or interference with other wireless networks (one of the networks that has the problem is remote mountain camp with no other camps/electronics within 20km).
Tip - Netgear has a beta release firmware (version 13) that has taken my worst base station from doing this 3-4 times a week down to approximately once a week. While not ideal, it's BETTER. You can get the firmware by quoting Issue ID 2389.
I was just talking to them today and they've now recommended that I change my "Network Authentication" from "WPA-PSK & WPA2-PSK" to just "WPA2-PSK". Apparently there's a known issue with that too. I've made the change but it'll likely take a week or more before I know the results.
What Network Authentication setting do you guys have? - bramschats1AspirantI'm also using security mode WPA-PSK & WPA2-PSK.
Maybe it has something to do with this security mode indeed.
In the mainwhile, is it possible, since it is a linux based wap to change the crontab to restart the access point every day?
Hope someone from netgear can help us out. - rilexAspirant
Tip - Netgear has a beta release firmware (version 13) that has taken my worst base station from doing this 3-4 times a week down to approximately once a week. While not ideal, it's BETTER. You can get the firmware by quoting Issue ID 2389.
Does this beta fix the security issues with the WAPs admin site? - bramschats1AspirantIs there any news on this topic?
Hope someone has some good testresults.... - AmberworksAspirantJust curious whether you'd gotten any further with this, I've got two WNAP210's on-site with the latest firmware 2.0.12 and have been experiencing the same problem.
Oddly they've worked perfectly for nearly 6 months, it's only in the last month that 1 of them has fallen over twice and required a reboot.