Results 1 to 11 of 11

Thread: Unable to access Netgear WNAP210

  1. #1
    Join Date
    Jul 2011
    Posts
    54

    Unable to access Netgear WNAP210

    I have an access point WNAP210 and is working fine except for one strange thing. They usually have 1 or 2 clients connected to the access point, but every three weeks I have to reboot the access point for the reason that the client cannot connect to the WNAP210. After reboot everything works fine again, but after a few weeks you have to restart again. What can cause this difficulty?

  2. #2
    Join Date
    Jul 2011
    Posts
    107

    Re: Unable to access Netgear WNAP210

    One that accessed through the admin page? If so, what say the records, anyway? FWIW, my WNAP210 running firmware 0.12 currently has an uptime of 23 days, but has been running longer.

  3. #3
    Join Date
    Jul 2011
    Posts
    54

    Re: Unable to access Netgear WNAP210

    check my log
    Code:
    IEEE 802.11: disassociated
    Sep 19 08:26:57 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
    Sep 19 08:27:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
    Sep 19 08:27:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
    Sep 19 08:27:12 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
    Sep 19 08:27:15 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request

  4. #4
    Join Date
    Mar 2009
    Posts
    1,221

    Re: Unable to access Netgear WNAP210

    Quote Originally Posted by Kazmierz View Post
    check my log
    Code:
    IEEE 802.11: disassociated
    Sep 19 08:26:57 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
    Sep 19 08:27:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
    Sep 19 08:27:00 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: disassociated
    Sep 19 08:27:12 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: associated
    Sep 19 08:27:15 SDK daemon.info hostapd: wifi0vap0: STA 3c:74:37:58:f8:51 IEEE 802.11: deauthenticated due to local deauth request
    I am experiencing this exact trouble with one of my clients. That seemed to work enhanced for a time, restricting the use of 20 MHz channels, although is now beginning to experience the same trouble - the Access Point will sometimes work, but not always. There are 2.3 only wireless devices (IPAD and iPhone).

  5. #5
    Join Date
    May 2008
    Posts
    1,304

    Re: Unable to access Netgear WNAP210

    I also limit my Access point to 20 MHz as dynamic causes 20/40 .I have to disconnect t accidentally.

  6. #6
    Join Date
    Nov 2008
    Posts
    1,066

    Re: Unable to access Netgear WNAP210

    I am having an identical problem on several sites. For more than a month have been supported by the solution of this Netgear. We have all the basics as the location of base stations, cables, power supply and the unit itself. We have restored the factory and tainted the location of the units. We have confirmed that the trouble is not a precise client or interference with other wireless networks (one network that has the problem is the remote mountain camp with no other fields / electronic components within 20 km).

    Council - Netgear has a beta firmware (version 13) has been my worst base station to do this 3-4 times a week to about once a week. While not perfect, is improved. You can acquire the firmware with a date of issue .

    I just talked to them today and have now recommended that I change my "Network Authentication" to "WPA-PSK and WPA2-PSK" simply "WPA2-PSK". Apparently there is a known problem with that too. I made the switch, but most likely take a week or more before knowing the results.

  7. #7
    Join Date
    Jul 2011
    Posts
    100

    Re: Unable to access Netgear WNAP210

    I'm also using the security mode WPA-PSK and WPA2-PSK.Maybe it has something to do with this security mode in effect.In mainwhile is possible, since it is a wap based Linux to change the confab to restart the access point every day?

    Netgear hope someone can help us.

  8. #8
    Join Date
    Mar 2010
    Posts
    295

    Re: Unable to access Netgear WNAP210

    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 think beta release will fix security troubles with WAP site administrator.

  9. #9
    Join Date
    Mar 2010
    Posts
    242

    Re: Unable to access Netgear WNAP210

    Just inquisitive if you had promoted with this, I have two WNAP210 in place with the most recent firmware 2.0.12 and have experienced the identical trouble.

    Strange as it has worked perfectly for almost 6 months, which is only last month that one of them has fallen more than twice and required a reboot.

  10. #10
    Join Date
    May 2008
    Posts
    945

    Re: Unable to access Netgear WNAP210

    But it turned out otherwise, after initiating an L2TP tunnel over the wireless connection. As a stability test ran for hours without problems before does not seem to be a pure accident.

    But in my opinion is very important to mention that high latencies are independent of the "deauthenticated application due to factors deauth - authenticated - partners' registry entries in my case. Because they are there, even before the latency increases.What was new for me this time is:

    Code:
    th: Could not stop RX, we could be confusing the DMA engine when we start RX up
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
    ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020
    ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
    ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020

  11. #11
    Join Date
    Nov 2008
    Posts
    1,001

    Re: Unable to access Netgear WNAP210

    WNAP210 is not based on OpenWrt (which contains no routing functionality, for example), but most of these use the same applications and drivers (madwifi, Busybox, etc.).Netgear has an "owner" WNAP210 pages that are not part of its distribution OSS, but these pages are easily visible from SSH.

    I decided to change the access point on my site WPA210 clients to another access point to another brand. It only seems to work the way it should and has to restart the AP each week.I tried to supply my clients with all Netgear products, but I think I have to change my policy.

Similar Threads

  1. Unable to access management console on Netgear WPN824EXT
    By R.Madhvan in forum Networking & Security
    Replies: 5
    Last Post: 10-03-2012, 04:03 AM
  2. Unable to access configuration page of Netgear WNR2000
    By Pirateous in forum Networking & Security
    Replies: 5
    Last Post: 09-03-2012, 10:37 PM
  3. Replies: 6
    Last Post: 19-09-2011, 06:38 AM
  4. Internet access behind Netgear router in Windows
    By Theodore in forum Networking & Security
    Replies: 3
    Last Post: 03-12-2008, 05:43 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,620,255.00413 seconds with 17 queries