NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi IP Address Range
The default DHCP range is 192.168.1.2 to 192.168.1.254.
I seem unable to modify this to be able to use 192.168.xx.yy or 172.16.xx.yy.
Is this just me or is this a limitation on the Orbi ...
Thx for your examples.
172.16.xx.yy was just an example as I tried that as well for completeness, I would probably stick with 192.168.xx.yy.
I was using Chrome browser and my Orbi is configured as a router interfacing to a BT modem. My BT HomeHub 5 offers a DHCP Network Range of, for example, 172.16.0.64 - 172.16.255.254 (which was partly why I tried using 172.16.xx.yy) so it is not an ISP limitation.
I notice that you were able to set 192.168.0.100 thru .200 but have you managed to change the third field/octet i.e. 192.168.10.100 or 192.168.20.100 so that theaddrtess range would be, for example, 192.168.0.100 to 192.168.10.200?
Well for one you can't use a router on the same IP address and subnet like that.
If your modem already has a built in router and uses 172, then the only 172 address that the Orbi can use is on it's WAN port. The LAN side would need to be 172.17.xx.yy. This should work on the LAN side of the Orbi.
And no you can't use 192.168.0.100 to 192.168.10.200 as a LAN side IP address range. Has to be .0.100 to .0.254 or .10.100 to 10.254.
3rd Octet has to be the same for begining address to ending address range.
Modem Combo Units:
Couple of options,
1. Configure the modem for transparent bridge mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, LAN to LAN and configure AP mode on the Orbi router
FURRYe38 wrote:
And no you can't use 192.168.0.100 to 192.168.10.200 as a LAN side IP address range. Has to be .0.100 to .0.254 or .10.100 to 10.254.
3rd Octet has to be the same for begining address to ending address range.
Is this a hard limitation? Is there a way to have the DHCP range span more of the subnet (e.g. 192.168.0.100 - 192.168.1.250 with a subnet mask of 255.255.254.0)? If not, I guess I'll have to rethink what part of the subnet I use for static IPs... Basically my only option will be to use 192.168.0.X for DHCP and 192.168.1.X for static.
toddrob wrote:
Is this a hard limitation? Is there a way to have the DHCP range span more of the subnet (e.g. 192.168.0.100 - 192.168.1.250 with a subnet mask of 255.255.254.0)? If not, I guess I'll have to rethink what part of the subnet I use for static IPs... Basically my only option will be to use 192.168.0.X for DHCP and 192.168.1.X for static.
This is not a hard limitation. I think it's just a software bug that the GUI does not change the allowed DHCP range when you change the netmask. If you think it's important for you to have that big range of IP addresses then please report this to NG Support and I hope that this can be fixed in coming releases. Otherwise the 2-254 DHCP range is quite big for a "normal" home user. It goes without saying that all the other addresses within the netmask that you set in Orbi can be used for static IP addresses.
My complimentary 90 days of support has ended. It looks like I have to purchase premium support in order to report a bug. Is that correct or am I missing something?
