NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
I did not have any problems with previous version, but I went ahead and updated to the beta.
Now on the satellite I am getting disconnects... but just one device. It's a La Crosse c84343 weather station. It constantly (like once a minute) disconnects and then comes back online and requests DHCP address. My log is now filled with DHCP messages from that device. If it helps, that device is quite close to the satellite.
I have not done a hard reset of the satellite - I will do that next.
So far, this seems to be my only issue with the beta (knock on wood) but like I say, this is a new issue.
Jeremyinsfwrote:
Now on the satellite I am getting disconnects... but just one device. It's a La Crosse c84343 weather station. It constantly (like once a minute) disconnects and then comes back online and requests DHCP address. My log is now filled with DHCP messages from that device. If it helps, that device is quite close to the satellite.
This issue is particular to the La Crosse weather station. For whatever reason, it gets very confused when both a 2.4G and 5G share the same SSID.
If you call their support line and chat a bit you will hear this about other routers and brands that share a common SSID. The trick to get it working again is to turn off the SSID broadcast for 5G (under Advanced wireless setup), then factory reset the La Crosse, link it up to the 2.4G SSID (which is the only one now being broadcast), power cycle the LaCrosse once the setup is complete and then re-enable SSID broadcast on 5G.
Make sure you are running the latest firmware on the LaCrosse as well.
This is not an Orbi issue but rather a LaCrosse issue that they are aware of.
Thanks for the info. Will definitely do what you suggest. However - why is this now a problem with the Orbi firmware update, when I had no problems before?