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

WAC720 LOCKING UP

redtech116
Aspirant

WAC720 LOCKING UP

Having a radom lockup issue...on two different wac720 units at different sites

the wireless just stops, can not log into the unit,

disconnect/reconnect ethernet has no effect.

Have to power cycle the units for them to come back..

using the current firmware.

one unit on POE another using an AC power adpter...

have reset and resetup the unit once already.

logs for one after rebooting..

 

[Jan 28 2017 19:20:08] [info] hostapd[1352] STA 18:a6:f7:94:87:f8 associated with BSSID 2c:30:33:08:a4:20
[Jan 28 2017 19:20:08] [info] hostapd[1352] Assoc request from 18:a6:f7:94:87:f8 BSSID 2c:30:33:08:a4:20 SSID Hell-Fire-69
[Jan 28 2017 19:19:51] [err] mDNSResponder mDNSPlatformRawTime went backwards by 51998735 ticks; setting correction factor to 954928979
[May 31 2016 16:00:49] [warn] dman[1107] DHCP-client: Interface brtrunk obtained lease on new address 192.168.1.103.

[May 31 2016 16:00:49] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:45] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:44] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:43] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:42] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:40] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:40] [info] hostapd[1352] STA 48:a1:95:cc:78:dd associated with BSSID 2c:30:33:08:a4:20
[May 31 2016 16:00:40] [info] hostapd[1352] Assoc request from 48:a1:95:cc:78:dd BSSID 2c:30:33:08:a4:20 SSID Hell-Fire-69
[May 31 2016 16:00:40] [err] hostapd[1352] trying to deauthenticate to station 48:a1:95:cc:78:dd, but not authenticated
[May 31 2016 16:00:40] [err] hostapd[1352] trying to update accounting statistics, station 48:a1:95:cc:78:dd not found
[May 31 2016 16:00:40] [info] hostapd[1352] STA 48:a1:95:cc:78:dd deauthed from BSSID 2c:30:33:08:a4:20 reason 3: STA is leaving IBSS or ESS
[May 31 2016 16:00:39] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:38] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:36] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:36] [info] hostapd[1352] STA d8:49:2f:26:2b:e1 associated with BSSID 2c:30:33:08:a4:20
[May 31 2016 16:00:36] [info] hostapd[1352] Assoc request from d8:49:2f:26:2b:e1 BSSID 2c:30:33:08:a4:20 SSID Hell-Fire-69
[May 31 2016 16:00:35] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:35] [debug] hostapd[1352] station: 48:a1:95:cc:78:dd deauthenticated
[May 31 2016 16:00:35] [info] hostapd[1352] STA 48:a1:95:cc:78:dd disassociated from BSSID 2c:30:33:08:a4:20 reason 8: Sending STA is leaving BSS
[May 31 2016 16:00:30] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:24] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:21] [info] hostapd[1352] Send failed (to server 192.168.1.1) - maybe interface status changed - try to connect again

[May 31 2016 16:00:21] [info] hostapd[1352] STA 48:a1:95:cc:78:dd associated with BSSID 2c:30:33:08:a4:20
[May 31 2016 16:00:21] [info] hostapd[1352] Assoc request from 48:a1:95:cc:78:dd BSSID 2c:30:33:08:a4:20 SSID Hell-Fire-69
[May 31 2016 16:00:18] [info] dman[1107] SSL certificate generated for Clusterd
[May 31 2016 16:00:16] [info] hostapd[1352] STA d8:49:2f:26:2b:e1 associated with BSSID 2c:30:33:08:a4:20
[May 31 2016 16:00:16] [info] hostapd[1352] Assoc request from d8:49:2f:26:2b:e1 BSSID 2c:30:33:08:a4:20 SSID Hell-Fire-69

 

Model: WAC720|2x2 Wireless-AC Access Points
Message 1 of 80

Accepted Solutions
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

All

 

We have addressed this issue in the latest firmware. Please download here

 

Thanks

Raghu

View solution in original post

Message 78 of 80

All Replies
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

Hi redtech116

 

Sorry to hear this issue. Could you please share the following to understand more ?

- How many wireless clients are trying to connect WAC720 AP?

- Are you seeing issue on 2.4Ghz radio or 5 Ghz or both?

- Is it possible to share wireless client details? ( Is it mobile devices or laptops? share model details)

- Share those logs before you do AP reboot

- I guess you are using latest firmware 3.6.12.0

- WAC720 AP configuration file

 

Thanks

Raghu

 

Message 2 of 80
redtech116
Aspirant

Re: WAC720 LOCKING UP

- How many wireless clients are trying to connect WAC720 AP? between 0 and 4 at this site

- Are you seeing issue on 2.4Ghz radio or 5 Ghz or both? the whole AP locks up..no throughput on anything

- Is it possible to share wireless client details? ( Is it mobile devices or laptops? share model details) 1-iphone / 1 - mac / 1 - windows 10 PC / 1 - android phone

- Share those logs before you do AP reboot? i don't have a remote syslog server setup yet / so all longs are kinda lost after reboot

- I guess you are using latest firmware 3.6.12.0 / yes

- WAC720 AP configuration file  / will post later tonight

Model: WAC720|2x2 Wireless-AC Access Points
Message 3 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

Hi redtech116

 

Thanks for the info, It would be nice if you mention the model of those wireless clients ( Windows, iphones, andriod and macs) ? Are you connecting these clients to 2.4 G radio or 5 Gh?

Please attach the AP confg as well. Logs would help more if you can attach if you have taken during issue.

 

Thanks again

Raghu

Message 4 of 80
redtech116
Aspirant

Re: WAC720 LOCKING UP

 

why can I not attach a file here...? I can attach a picture but not a file..come on NETGEAR

the AP completely locks up , can not log into it wirelessly or wired...

some are on the 5 some are on the 2.4 radio's..take your pick..

this is about all i can give anyone..

 

https://www.dropbox.com/s/40z7qcprc0g7rlo/config.xml?dl=0

 

Model: WAC720|2x2 Wireless-AC Access Points
Message 5 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

I would like to get in on this, I am having the exact same issue.  All the lights stay on but it kicks everything off.  We have 1 garage door opener, 3 asus laptops, 2 android phones, a ring door bell, and ring door bell speaker and that is it.

I also thought it was a hardware issue so Netgear replaced mine, got the new one programmed and same issue started again.  

Message 6 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

Hi DCMData

 

 

Are you able to login to AP UI? If yes Could you please send us the AP logs? We will take a look at it.

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

 

Thanks

Raghu

Message 7 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

Yes all lights are solid, not blinking.  Sometimes traffic light is off, next to the power light, but that is 1 out of every 10 times.  Sometimes it will stay up for days, some days I reset it 6 times a day.  Today I have reset it 3 times so far.

When it freezes there is no logging into it, I cannot ping it or anything from a hardwire connection on the network.  Other things I have tried is different POE injectors and a POE switch, thinking it was a power thing.  It is not where I can plug it in to an outlet.

 

This is all that is in the logs right now...

[Mar 8 2017 02:11:59] [info] hostapd[1345] STA 00:1d:c9:29:6c:22 associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:11:59] [info] hostapd[1345] Assoc request from 00:1d:c9:29:6c:22 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:57] [info] hostapd[1345] STA 74:f0:6d:20:4d:08 associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:57] [info] hostapd[1345] Assoc request from 74:f0:6d:20:4d:08 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:54] [info] hostapd[1345] STA fc:c2:de:8f:10:41 associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:54] [info] hostapd[1345] Assoc request from fc:c2:de:8f:10:41 BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:46] [info] hostapd[1345] STA d0:22:be:f5:50:0f associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:46] [info] hostapd[1345] Assoc request from d0:22:be:f5:50:0f BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:45] [info] hostapd[1345] STA 64:52:99:48:26:5d associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:45] [info] hostapd[1345] Assoc request from 64:52:99:48:26:5d BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:42] [info] hostapd[1345] STA c0:56:27:4e:4b:e6 associated with BSSID 2c:30:33:98:8f:b0
[Mar 8 2017 02:10:42] [info] hostapd[1345] Assoc request from c0:56:27:4e:4b:e6 BSSID 2c:30:33:98:8f:b0 SSID ComeTakeIt5G
[Mar 8 2017 02:10:37] [info] hostapd[1345] STA f4:b8:5e:4d:5e:5b associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:37] [info] hostapd[1345] Assoc request from f4:b8:5e:4d:5e:5b BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:35] [info] hostapd[1345] STA dc:85:de:89:12:ff associated with BSSID 2c:30:33:98:8f:a0
[Mar 8 2017 02:10:35] [info] hostapd[1345] Assoc request from dc:85:de:89:12:ff BSSID 2c:30:33:98:8f:a0 SSID ComeTakeIt
[Mar 8 2017 02:10:27] [info] dman[1107] SSL certificate generated for Clusterd
[Mar 8 2017 02:10:27] [err] mDNSResponder mDNSPlatformRawTime went backwards by 989200818 ticks; setting correction factor to -127739691

Message 8 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

Thanks for the info. I think these logs are taken after the AP reset. Do you have any external syslog setup? Please share the logs before the reboot.

 

Raghu

Message 9 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

I cannot login to it when it is froze, there is not logs to be shown.  It does not communicate in any way.  If there is a way to output logs to somewhere I would set it up, is there some instructions on how to do that, I don't see it in the settings.

Message 10 of 80
RaghuHR
NETGEAR Expert

Re: 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

Message 11 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

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

Message 12 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

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

Message 13 of 80
ratherman
Tutor

Re: WAC720 LOCKING UP

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...

Message 14 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

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

Message 15 of 80
DeNeil
Aspirant

Re: WAC720 LOCKING UP

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.

Message 16 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

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.

Message 17 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

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.

Message 18 of 80
ratherman
Tutor

Re: WAC720 LOCKING UP

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.

Message 19 of 80
ratherman
Tutor

Re: WAC720 LOCKING UP

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...

Message 20 of 80
DeNeil
Aspirant

Re: WAC720 LOCKING UP

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..

Message 21 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

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.

Message 22 of 80
DeNeil
Aspirant

Re: WAC720 LOCKING UP

My money is on the Samsung!

Message 23 of 80
DCMData
Tutor

Re: WAC720 LOCKING UP

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??

Message 24 of 80
RaghuHR
NETGEAR Expert

Re: WAC720 LOCKING UP

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

Message 25 of 80
Top Contributors
Discussion stats
  • 79 replies
  • 11205 views
  • 1 kudo
  • 11 in conversation
Announcements