NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Your experience with Firmware 2.2.1.210 released as of 10/3/18
The other long thread on the new firmware is useless and has become a tech support thread. Please only post your experience after upgrading to the new firmware, good or bad. I'd like to see everyone'...
I have not had any issues in fact I did not know that my system was updated to this release until I checked after browsing the community site. The update was seamless as no one complained about noticing an outage (there are 4 of us plus friends and other family).
In terms of the environment, I live in a 2.5 story townhouse with a lot of neighbors also broadcasting wifi signals (I see over a dozen networks on my phones wifi signal strenght app). The Orbi runs in router mode attached to my Arris Surfboard SB6183 cable modem. IP service is from Spectrum. I have about 8 devices on all of the time not including phones, laptops and TVs. I don't know if it makes a difference, but I assigned specific IP addresses to the devices that were on most or all of the time. I use the range 148.192.168.0x for the Orbis, 148.192.168.1x for wired connections and start the DHCP range at 148.192.168.2x. I do not use remote management.
The only issue I am currently having has to do with the list of devices that are not currently connected. It reports almost every connection as having been wired when in fact they were wireless though one of the Orbi satellites.
Glad it's working for you.
Thats an odd IP address pool, however if it works for you. :smileywink:
Is Daisy Chaing Disabled or Enabled on your router? If you updated to recent FW v.210, try enabling Daisy Chain. Some have mentioned that this seems to be working in reverse order, enabling means disabled actually. May effect how devices are being reported. I believe that this may fix your one issue...
73Bruin wrote:
I have not had any issues in fact I did not know that my system was updated to this release until I checked after browsing the community site. The update was seamless as no one complained about noticing an outage (there are 4 of us plus friends and other family).
In terms of the environment, I live in a 2.5 story townhouse with a lot of neighbors also broadcasting wifi signals (I see over a dozen networks on my phones wifi signal strenght app). The Orbi runs in router mode attached to my Arris Surfboard SB6183 cable modem. IP service is from Spectrum. I have about 8 devices on all of the time not including phones, laptops and TVs. I don't know if it makes a difference, but I assigned specific IP addresses to the devices that were on most or all of the time. I use the range 148.192.168.0x for the Orbis, 148.192.168.1x for wired connections and start the DHCP range at 148.192.168.2x. I do not use remote management.
The only issue I am currently having has to do with the list of devices that are not currently connected. It reports almost every connection as having been wired when in fact they were wireless though one of the Orbi satellites.
I use specific IP asssignments because I wanted to avoid potential conflicts. The wired devices in my configuration are either always on (e.g. Ooma, Roku) or where I want to set a specific IP for administration (my laptop in wired mode).
My system has Daisy Chaining enabled (and always has since that functionality was enabled) but the devices are separated far enough so that they don't chain. I am looking at getting an additional RBS50 or 40 to speed up connectivity in our large kitchen), it would probably chain if I don't wired the boxes.
What Furry means by "odd address pool" is that your internal LAN addresses are outside the ranges of standard internal addresses.
https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses
