WAC720 LOCKING UP

Please refer the page 69 -70 on how to setup syslog server.

http://www.downloads.netgear.com/files/GDC/WAC720/WAC720_730_UM_EN.pdf

You can install any free third party syslog server on windows/linux box.

thanks

Raghu

Lots of debug stuff tonight...Have reset it 4 times today...

[Mar 9 2017 04:28:28] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:28:28] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:26:29] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthenticated for reason 15: 4-way handshake timeout
[Mar 9 2017 04:26:29] [info] hostapd[1343] Station 74:f0:6d:20:4d:08 had an authentication failure, reason 16
[Mar 9 2017 04:26:25] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 associated with BSSID 2c:30:33:98:8f:a0
[Mar 9 2017 04:26:24] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 associated with BSSID 2c:30:33:98:8f:a0
[Mar 9 2017 04:26:24] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:26:24] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:26:24] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:26:24] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:26:24] [err] hostapd[1343] trying to deauthenticate to station 74:f0:6d:20:4d:08, but not authenticated
[Mar 9 2017 04:26:24] [err] hostapd[1343] trying to update accounting statistics, station 74:f0:6d:20:4d:08 not found
[Mar 9 2017 04:26:24] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:22] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:22] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:25:22] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:22] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:22] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:25:22] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:22] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:22] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:25:22] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:21] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:21] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:25:21] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:21] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:21] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated
[Mar 9 2017 04:25:21] [info] hostapd[1343] STA 74:f0:6d:20:4d:08 deauthed from BSSID 2c:30:33:98:8f:a0 reason 3: STA is leaving IBSS or ESS
[Mar 9 2017 04:25:21] [info] hostapd[1343] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 9 2017 04:25:21] [debug] hostapd[1343] station: 74:f0:6d:20:4d:08 deauthenticated

Thanks for the logs. From the log at appears wireless client is leaving the BSSID. Do you know/have any other AP in the network which you have connected earlier? How busy is your wireless environment is?  Can you can please login to AP CLI via SSH  ( admin/password) and send us these detail?

1) Check wlan0 noise: should be around -90 dBm
                - wl -i wlan1 noise 

                - wl -i wlan0 noise

2) Check wlan0 utilization: > 70 % means a lot of contention for the wireless medium
                - get radio wlan1 wlan-util

                 - get radio wlan0 wlan-util
3) Check for the data rate of last packet in client info: data rate low means client is sending packets at low phy data rate that could be due to location or high network utilization
                - get association detail (-- collect only the spcific client information alone)
                - wl -i wlan1 sta_info <50:55:27:f1:f9:24>
4) Check for AP CPU and Memory utilization
                - cat /proc/meminfo
                - ifconfig
                - brctl showmacs brtrunk
                - netstat

                - top

BR

Raghu

I just wanted to interject that we are having the same problems - I have (4) WAC720's at my location and they are working fine.  We have one at my partners location and we have to reboot it all of the time.  Sometimes 3-6 times a day.  Not cool...

Hi ratherman

Could you please let us know your issues in details to understand your issue is same as previous one or new one?

- Send us the AP logs and refer the this thread to see how you can collect .

- Are you seeing the issue on 2 Ghz or 5 Ghz radio? Or on both?

- What type of wireless clients that you are traying to connec to our AP? and how many?

-Are you seeing all LEDs are solid Green and not blinking?

- Are you able to login to AP UI?

- How busy is your wireless environment is?  Can you can please login to AP CLI via SSH  ( admin/password) and send us these detail?

1) Check wlan0 noise: should be around -90 dBm
                - wl -i wlan1 noise 

                - wl -i wlan0 noise

2) Check wlan0 utilization: > 70 % means a lot of contention for the wireless medium
                - get radio wlan1 wlan-util

                 - get radio wlan0 wlan-util
3) Check for the data rate of last packet in client info: data rate low means client is sending packets at low phy data rate that could be due to location or high network utilization
                - get association detail (-- collect only the spcific client information alone)
                - wl -i wlan1 sta_info <50:55:27:f1:f9:24>
4) Check for AP CPU and Memory utilization
                - cat /proc/meminfo
                - ifconfig
                - brctl showmacs brtrunk
                - netstat

                - top

Hi

I have the same issue - basically I have isolated the problem to my Samsung S7 - as long as I keep the Samsung S7 away from the access point, everything else is fine - perhaps it's your android devices doing the same.

That is good to know, I have 4 andriod devices connected...3 of them are Samsungs, none are S7.  If that is the problem then Netgear has a major bug in their stuff...I have a second access point from Linksys I will bring up and move the android devices to it and see if it makes a difference.

I set a personal record yesterday of 8 reboots....It could be my Samsung S5, seems to happen more when I get home.  Wife says it is fine until I get home, so I am the source of the all the wireless problems.  My Samsung S5 is hooked to the 2.4, maybe I will hook it to the 5 and see if that makes a difference.  Not sure what an andriod device could do to take down a WAP, but worth a shot.  By the way it is connected to other Wifi all the time when I am at difference clients, inlcluding some WAC730's...it has never taken them down.

In my location - I have a Motorola DROID TURBO with four WAC720's in ensemble mode and have no issues.  At my partner's location - where he is having an issue - they have three Android phones - I am checking on what models they are and will report back.

Just a follow-up, at the location that is having issues - I have a user with Google Pixel, Motorola DROID TURBO 2, Samsung Galaxy S7 - wonder if it is the Galaxy S7 that is causing the issue...

Hi

A further bit of info - the access point is connected to a POE port on a netgear switch. When the Samsung takes the WiFi down, it only takes the data down - it remains powered up. Also, when the Samsung is then removed from the vicinity of the access point, I can reset the switch port, which appears to have been disabled - weird - but I have established that it is only the Samsung over the last few days - iPhones, Macs and Windows' machines all ok..

More info, I was just informed that mine has locked up.  I am not there so my phone is not connected.  Still have S4, S4 mini, Asus W700 tablet, 2 asus laptops, Liftmaster garage door opener, and Ring door bell attached.

My money is on the Samsung!

So netgear, what is the fix?  Can and andriod device really take down a whole access point?  What could they be doing differently than every other wireless device on the network??

All,

Sorry to hear your issues. We are working on similar issues that we have observed on high priority .  As of now we are not aware there are any specific issues with Samsung android devices. We will reach you individually if we need more info. Once we know the root cause we will come up with hot fix ASAP.

Thanks

Raghu

Last night I brought up one of my Linksys WAP.  I moved all android devices to it.  They are all Samsung something.  The Netgear WAC720 did not lock up all last night.  I will keep you all updated as to how it works from this point.

Well last night it locked up once and had to reboot it.  There is not a single android device connected to it now.  Unless the ring door bell or garage door opener is android.  So it is not my Samsung clan causing my issue.

Thanks for the details. We are actively working on this issue. Can please provide the model details of ring door bell  and  garage door opener?

Well ring only makes 2 door bells right now, so there really is no model number, it is the standard not the pro, but the garage door opener is a liftmaster is a 8557W Elite Series opener.

Thank you. Do you have the  console connected to AP? If yes please give the console output by executing these commands? Please execute these commands before you start test to till you hit the issue

echo 8 > /proc/sys/kernel/printk
echo Y > /sys/module/printk/parameters/time

You need to redirect all the console log to to file and send it.

You can refer the folloing video how to redirect console out put to a file.

the https://www.youtube.com/watch?v=ZvNNoP7tivQ

When hang happens did you tried hard  factory reset ? Was your AP responding for that? these are important data points for us debug further.

Thanks again.

I don't have a console connected to the AP, but in my testing I did do a factory reset and reprogrammed from scratch.  Also in above I stated that I called support for this issue and they replaced the access point under warranty, so this is a different access point havig the same issue I had before.  I did a factory reset on both before re-programming them.  I did not restore a backup.

The AP is hanging on the ceiling, so I did not do a reset with the button because it is hard to reach, I just did a power reboot from the POE injector then went in and factory reset it.  I did not do it from the button.

I can try that next time if you like, it is working better and has only locked up once since I got all the Samsung devices off of it, None of which are an S7.

Any updates, I only have the Garage Door opener, ring door bell and 2 asus laptops, hardly a load at all.  Since I got all the andriod devices off it only locks up about 1 time a day.

When the issue happens are you able to ping the IP address of the WAC7xx AP? If yes can you please do the SSH to the AP and send us the following CLI command output?

dmesg  => copy the entire message in text file and send us

top    => you can send us  this command snapshot

When it locks up I can do nothing but reset it...Can't ping, can't do anything.  Have to unplug the power to the POE injector and plug it back in.

I was just pulling the plug, but discovered that it appears to disable the port on the switch - I can log into the switch and re-enable from there.