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?
I can't really experiment right now, but have you tried changing the subnet mask and then applying the changes? I have the first three octets of the DHCP pool grayed out, and I tried changing the subnet mask to see if the third octet would become editable (it didn't), but I didn't want to apply the changes and disrupt connections. It's possible the DHCP pool is derived from the router's IP address and subnet mask that have been applied, so by changing the IP and/or subnet mask, the portion of the DHCP pool addresses that can be edited will change as appropriate.
Though, I just tested changing the IP address, and the DHCP pool addresses changed immediately, without applying, as soon as I moved the cursor out of the changed octet's field, so maybe not. It might just be lazy programming on their part (maybe even just on the GUI, and the router itself is actualy capable of handling it), and they just assume home users won't need more than 254 IP addresses, so they have it set to copy the first three octets from the IP address to the DHCP pool, regardless of subnet mask. It's possible you can successfully use /23, etc. if you do it from the command line. At least from the web GUI, it seems the third octet in the Orbi's IP address will define the third octet in the DHCP pool.
As for your ISP router allowing 172.16.0.64 - 172.16.255.254, that's a function of the router (and, perhaps, the provisioning by the ISP if it's a modem/router combo unit), but not anything the ISP would be able to restrict on your Orbi. If you had a commercial-grade router, you could use 10.0.0.0 as your network, and your ISP would not know, care, or be able to prevent it.
- With smart home devices that connect to WiFi it is becoming increasingly possible to have over 200 devices on your network. This is going to become even more of an issue as time goes on and the number of smart devices grows.
randomousity wrote:
.......... and I tried changing the subnet mask to see if the third octet would become editable (it didn't), but I didn't want to apply the changes and disrupt connections. It's possible the DHCP pool is derived from the router's IP address and subnet mask that have been applied, so by changing the IP and/or subnet mask, the portion of the DHCP pool addresses that can be edited will change as appropriate.
......
I tested that and the DHCP range did not change after Applying the changes. In fact I lost all my 48 IP address reservations as a result and had to enter them again :(
Is seems that Orbi is currently designed to have a limited sized DHCP pool, assuming that a home user will not need more than than dynamic 251 addresses. The rest of the subnet addresses can be used for static IP addresses if needed.
