NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi assigning wrong DHCP IP Space
I have an odd issue where Orbi will assign some devices the wrong IP address space. My default space is 10.0.0.x and I have some devices connected wirelessly that get assigned an ip address of 192.16...
If your going to use the RBR in router mode behind another router, I would make sure you place the RBRs WAN IP address it gets from the ISP router into the DMZ on the modem. Will help with NAT problems when in this kind of configuration.
HazardousTim wrote:I have an odd issue where Orbi will assign some devices the wrong IP address space. My default space is 10.0.0.x and I have some devices connected wirelessly that get assigned an ip address of 192.168.2.x. Other than assigning static IP Addresses I'm not sure how to resolve the issue.
Anyone else run into this problem?
It is already getting its NAT IP address via DHCP from the AT&T Router.
FURRYe38 wrote:If your going to use the RBR in router mode behind another router, I would make sure you place the RBRs WAN IP address it gets from the ISP router into the DMZ on the modem. Will help with NAT problems when in this kind of configuration.
HazardousTim wrote:I have an odd issue where Orbi will assign some devices the wrong IP address space. My default space is 10.0.0.x and I have some devices connected wirelessly that get assigned an ip address of 192.168.2.x. Other than assigning static IP Addresses I'm not sure how to resolve the issue.
Anyone else run into this problem?
The DMZ or IP pass thru would be recommneded if your using the RBR in router mode behind the ISP Modem/router:
https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NATI have also seen this. My Dish receiver will end up with an IP of 169.* where it should be 192.*. I have not narrowed down the source. I reboot my ISP modem (bridged), personal router, Orbi (router - AP mode - and satellites) - the receiver just does not want to let go of 169. I have to reset the Dish receiver and then it grabs the correct IP. It is almost like the Orbi router gets placed in Router mode briefly and hands out IPs before it flips to AP mode. However, in the meantime 169 gets assigned I guess until the lease expires??? - pure guess.
Anyway, reboot/restart the impacted device usually corrects it for me.
DISH Hopper or a different model?
I all have DISH Hopper system. 3 Joeys all wired to the hopper via separate segmented switches, away from primary home network, which connect directly to the back of the RBR. I would make sure your DISH devices are directly connected to the back of the host router.Occasionally I have to power OFF the Hopper and Joeys when changing routers as they don't seem to acquire an IP address correctly or could have been in IP address conflict which could lead to a 169 address. I haven't seen any 169s on the system. The DISH devices don't have any asssigned IP reservations.
You might assign IP address reservations the the DISH device(s). Be sure to power them OFF for 1 minuted then back on after a reboot of the RBR. May help with what your seeing.
theoak wrote:I have also seen this. My Dish receiver will end up with an IP of 169.* where it should be 192.*. I have not narrowed down the source. I reboot my ISP modem (bridged), personal router, Orbi (router - AP mode - and satellites) - the receiver just does not want to let go of 169. I have to reset the Dish receiver and then it grabs the correct IP. It is almost like the Orbi router gets placed in Router mode briefly and hands out IPs before it flips to AP mode. However, in the meantime 169 gets assigned I guess until the lease expires??? - pure guess.
Anyway, reboot/restart the impacted device usually corrects it for me.
