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?
My guess is there is something wrong with DHCP ....
You cannot set lease times ... which, at my office, days after people are gone, their device still shows up as "connected"
So far, my Ipad has not had a problem after giving it a static IP.
steve8411wrote:My guess is there is something wrong with DHCP ....
You cannot set lease times ... which, at my office, days after people are gone, their device still shows up as "connected"
So far, my Ipad has not had a problem after giving it a static IP.
The default DHCP lease time on the Orbi is 1 day (86400 seconds). It can be changed, but you need to be on the command line to do it:
# config set lan_lease=86400 # config commit [ now reboot the router to apply]
Just change the default value to whatever you want... with the usual caveat that if you are poking around on the command line and not sure what you are doing, you may just make things worse for yourself; but nonetheless, the option is there for those intrepid types.
EDIT TO ADD: I'm not sure that extending the DHCP lease time will actually fix anything in regards to the intermittent connectity drops that some clients seem to have. Personally, I prefer a longer lease time, but I've seen clients drop their connetion well before the current lease expires.Still seeing lots of disconnects on iPhone 7, iOS 11.2.6 even after trying this beta since about an hour after it dropped online. Very disappointing. I’ve tried every tweak and combination of tweak that exists on this forum, which I’ve haunted for about 9 months now.
Do a reset on both Satellite and router.
Also can try disabling MIMO, Daisy Chain and Fast Roaming to see if this helps any.
Jeremyinsfwrote: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.
