NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk R7000 Arlo SSID broadcast won't turn off Firmware V1.0.6.28_1.1.83
Earlier, I had downgraded the firmware to V1.0.3.80 because I was having unstable connection issues from the R7000. Downgrading seemed to have solved the stability problem, but I found that the Arlo ...
Are you doing a factory reset to defaults after changing the firmware each time? I strongly suggest you do. It almost sounds like the settings may be overlapping between firmware versions, so if you don't clear out the old ones, the firmware may be picking up old ones that are incorrect or meant for a different feature.
Hello searay,
Thanks for replying. My Smart Connect is already turned off, but the SSID is still being broadcasted with Arlo disabled.
Are you doing a factory reset to defaults after changing the firmware each time? I strongly suggest you do. It almost sounds like the settings may be overlapping between firmware versions, so if you don't clear out the old ones, the firmware may be picking up old ones that are incorrect or meant for a different feature.
Hello rpoffen,
I have done a factory reset somewhere along the process, but I can't recall when exactly. I would assume that the reset should turn off the Arlo broadcast feature by default. However, I will try factory resetting one more time to be sure.
Is it normal for a higher firmware feature to remain even after downgrading the firmware?
No
I switched back to 1.0.5.25 without any issues.
No, a feature would not remain that isn't coded in the old firmware, but all new features likely have some entry in the settings database that pertain to them. Depending on how this database is organized internally, it is possible that an area that is used by a new feature in the later firmware, means something else for the older firmware, thus can confuse the operation of the router. A good example apparently is the port forwarding feature which broke from 1.04 to 1.05+ unless you deleted and re-enetered the rules. Something was not the same in the way the settings were stored between the versions of firmware.
Performing a reset to defaults after loading new firmware should guarantee that the memory area used by that version of firmware for settings is set to a known, valid state.
The FW udate should fail unless a default is completed before updating. This would solve most problems before they even made here to another why me post.
Another factory reset did it. Ther Arlo SSID finally stopped broadcasting when I turned it off after the reset. It seems that the Arlo settings are kept even after downgrading. However, upgrading the firmware and resetting once more finally got the Arlo settings to respond correctly!
Today I updated once again to 6.28, Disabled arlo without a problem. The only issue I had sooooooooooooofar is some text is missing where you enter the e-mail settings. While UPNP was enabled all 5 QNAP ports were forwarded and working. I've since disabled it.
I've had this router since NG gave it to me. Between then and now something has changed, updates are a royal pain in the _$$ to preform with this" UPDATE for DUMMIES smart FW" .
I seem to have a new problem with this firmware. I wanted to test our new modem and played around with the settings to see the new speeds for 2.4 Ghz only and 5 Ghz only. When I turned off the 5 Ghz for both SSID and Wireless Router Radio, the network somehow still showed up in my list of wireless networks. I highly suspected that this was related to my earlier problems when the Arlo SSID kept being broadcasted, as some device recognized the broadcast as Arlo network while others recognized the broadcast as 5 Ghz network. When I would try to login to the mysterious 5 Ghz network, I would be unable to, providing more evidence that this was the Arlo network. So either something weird is happening due to this firmware update or my router has some hardware problems...
Has anyone else noticed problems simialr to this? Could someone try replicating what I did to see if it would happen again?