Orbi IP Address Range

FURRYe38
Guru - Experienced User
Aug 07, 2018
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
- toddrob
  Guide
  Aug 11, 2018
  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.
  - ekhalil
    Master
    Jan 01, 2019
    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.
randomousity
Luminary
Jan 02, 2019
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.
- broyuken
  Initiate
  Jan 02, 2019
  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.
  - ekhalil
    Master
    Jan 02, 2019
    broyuken wrote:
    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.
    
    I completely agree!
- ekhalil
  Master
  Jan 02, 2019
  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.

Forum Discussion