NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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
79 Replies
- FWIW we haven't had a lock up since I removed the AP's from Ensemble Mode and assigned them unique SSIDs. I've also purposely added three Samsung devices to rule that out - it doesn't seem to be causing a problem in my environment.
I'm monitoring the Syslog and waiting for a phone call letting me know the issue is back - the question for us is how long to we wait before pulling the devices and replacing them with something more stable.I have been working with Netgear support and they have given me a beta build that so far has fixed my problem, not a single lockup since I updated it last Friday. They are willing to give it to anyone else that wants to test it.
Support - how do we go about getting the beta?
Thanks,
John Rather
- I want!
Thanks - One for me too please!
Mine are all in standalone mode....
- Mine too
Hoping the beta will work for Ensemble mode also, since that was the primary reason for going with the WAC720's
- Ditto on that
- Ok I have an update and it is not a happy one - and for those keeping up with this thread, I'll lead off with this: I haven't yet installed the new beta firmware. I suspect that I will end up installing it because I've tried everything else under the sun to resolve this issue. But my confidence level in its ability to resolve this issue is quite low.
I have an open support ticket with a level two tech support agent, and I've also culled some information from a Reddit thread. Please pardon the repetition here. I want to be able to immediately send this text as an update to my ticket and also update the Reddit post.
Here is the issue that I am having: total connectivity loss on WAC720 access points. This means that clients cannot connect to the WAP via wifi nor can I ping the device via its static IP nor can I login to its web GUI. This has been well documented by others. When this occurs, all LEDs on the device turn solid. The only resolution for me and others is to power cycle the device. This began to occur for my client approximately three to four months ago. I have since replaced one WAP, verified wiring, factory reset each WAP, removed the Ensemble configuration, configured a unique SSID for each 2.4 and 5 ghz station, upgraded firmware, etc. the issues only present themselves over the wifi network associated with the WAC720s. No other device or client on the network is affected in any way at any time. Per advice on this thread, I have removed all Samsung devices from the network, and then intentionally added them back in. I've had no issues with Samsung devices for serveral days. Today, with zero Samsung devices on the network, two WAP's exhibited the lock-up that we have all been experiencing.
This is where I am at:
I've done everything that my tier two support agent has asked of me, no resolution. We had thought that removing the devices from ensemble mode and assigning unique SSID's would at least provide a data point for the technicians should it fail again, but they've released a new beta firmware without awaiting those results
From those that have tested the new beta firmware, I understand that you too have removed the devices from Ensemble Mode and are running in standalone, and many of you selected this WAP precisely for the ability to run them in ensemble.
I have installed a Syslog server, no one from support here or through my support ticket has requested any logs from it. No one has requested any configuration files, though I have offered them to both groups.
I'm very very very close to replacing these access points and calling it quits with Netgear as a whole.
Here is what would prevent that:
I think it is reasonable for your agents handling open support tickets to monitor and be aware of ongoing issues reported in these threads and for your agents on both ends to work collaboratively towards a solution. I shouldn't need to inform my level two agent that I've just recieved a beta firmware from a level three agent when I've been posting on this thread for a week or more.
I need to see a full resolution in place, or an admission that a full resolution isn't possible at this time, a reason why, and a timetable to expect a resolution (this refers to Ensemble Mode working as advertised).
Lastly I need to see some evidence of other users successfully deploying the beta firmware in an Ensemble environment.
I respectfully ask that those of you on these forums review my experience along with others and let me know if my expectations are out of line. We are all experiencing issues, and we have all done our part to troubleshoot them. I'm running short of patience with this and I'm sure that there are others at the same point.
Kind regards to all,
TylerHaving lock up issues as well. I have three WAC720s in Ensemble mode. Firmware version 3.6.12.0.
The problem started when I brought home my new Moto Z Force Droid. I am connecting to the network using the 5Ghz band. The only time the WAC720s lock up is when the Motorola phone connects to the network. All the lights go solid when the lockup occurs. In a few cases all the LEDs were solid except for the 2.4Ghz LED, it was off. After two of the WAC720s drop out the single remaining AP seems to work just fine. The network I have usually serves 10 - 20 wireless clients.
I've seen some workarounds by going to stand alone mode. I agree with Tyler, that isn't what I paid for. I was sold on the Ensemble mode which is why I purchased these units.
I would also be interested in the Beta firmware, Maybe I missed something, but does the Ensemble mode work?
Thanks,
Don
Hi Don
We appologize for the issue that you are facing. By any chance are you using captive portal feature? If possible please share you AP config. Are there any possiblitiy that you have console connected to WAC720 to share additional info for us?
We have the beta firmware which resolved other community user here received. You can use that and share your feedback. Please reach our support team to get the beta firmware .
Thanks
Raghu
Status Update:
Been running the BETA firmware for about 2 weeks now on 4 WAC720's in Ensemble mode. Lockup issues are less frequent but still there. Working with a support engineer and hopefully this can be resolved soon.
- I don't believe we've experienced a single lockup on the beta firmware in standalone mode. Glad I didn't try reverting back to Ensemble Mode yet!
I had this issue with WNDAP 350s (3 of them) and have just bought 3 x WAC730s thinking it was a hardware issue and that it was time for an upgrade anyway. I am still having the issue with the WAC730 despite them auto upgrading to the latest firmware (3.7.10.0) as I use business central to manage them. In my case the APs just randomly reboot.
In Business Central I have the option to upgrade the APs to beta versions (3.7.10.2 or 3.7.11). Should i attempt to upgrade?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
