NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi RB50 assigning IPs out of range, wrong connect types
Anybody have any ideas? I've had years of no-hassle use from my Orbi system, but I'm at wit's end with current troubles.
I have an RBR50 with satelites RBS50 and RBW30, connected to Comcast upstream via a Surfboard SB8200.
Main issue is my Orbi assigns out of range !P addresses in the 172. range. I've specified a range of 192.168.10-192.168-255, with some reserved IPs in the 192.168.1.2-9 range.
Orbi doesn't seem to assign nor reserve addresses properly, and is suddenly assigning 172.27.35.x addresses to random devices (both dynamic and reserved devices).
Some devices assigned 172 addresses work anyway, albiet slower, some (like my meetcircle device) are inoperable/unreachable since they aren't on the 'LAN'.
Now i'm noticing that some devices with 172 addresses are also specified as wired, but they are strictly wireless devices (like my Rachio).
I've done multiple reboots, removed/added devices, assigned IPs, upgraded to firmware v2.7.2.104.... nothing is working.
What is with the 172 addresses? Where do they even come from? Is my Orbi dead? Is 172 an internal/backhaul range? I noticed one of the satelites was in "Config Sync" status while assigned a 172 address.
Anybody seen this before or have any ideas?
jimslade wrote:i'll give the test a go. Now I'm super curious what else could be handing out IP addresses?? Cannot imagine what else has a DHCP server?!?
It is 99.999% certain that the Orbi is not assigning IP addresses that begin with anything besides 192.168.1.
So, either:
- devices are configured with static IP's that begin with 172, or
- some other DHCP server is giving out these addresses
You would probably remember assigning static IP's, so my money is on another DHCP server. Likely culprits include NAS servers and media devices. Some smart speaker systems attempt to network themselves.
I positively love capturing packets and looking at them with Wireshark, which puts me squarely in the uber nerd category.
Another simplistic question is, "what has been added to the network since things were fine?"
15 Replies
Has a factory reset and setup from scratch been performed since last FW update?
What Firmware version is currently loaded?
172s would not be coming from the RBR if you have setup the RBR for 192.
Afer a factory reset of the RBR and power cyle OFF of the ISP modem, set up the RBR off line from the modem and ALL other devices. Setup the IP address range from 192.168.1.100 to .200. You might even try using 192.168.0.1 as a different submet pool. .0.100 to .200.
Either one, then after it's setup, connect the RBR to the modem and connect just 1 wired PC to the RBR. Turn both ON and check the connections and such. Check for IP addressing on the connected devices page on the RBR.
Start graduating adding devices either 1 at a time or 2-3 at a time. Again checking connected devices page for IP addressing.
Make sure that you don't have any devices that have any kind of static configured IP addresses set ON the device. Static IP addresses are set ON devices, not the router. IP address reservations are set ON the router and not on devices.
no, didn't do factory reset. thanks for the steps... i'm hoping it doesn't come to that... sounds painful :)
jimslade wrote:Main issue is my Orbi assigns out of range !P addresses in the 172. range. I've specified a range of 192.168.10-192.168-255, with some reserved IPs in the 192.168.1.2-9 range.
Is it correct to assume that the "1" was left out of the description of the DHCP range? i.e. the DHCP pool runs from 192.168.1.10 to 192.168.1.255?
I suspect that there is now another DHCP server on the network. DHCP is a really primitive protocol. Devices broadcast a request and respond to the first DHCP server that answers. (Seriously, the first. They do not 'wait and see' how many responses they get. First means first.)
An easy way to confirm (or deny) this hypothesis would be to temporarily stop having the Orbi act as a DHCP server, then turn off some device and power it back on again.
- If it gets an IP address, there is another server.
- The Orbi log file should not show a DHCP assignment (because the Orbi did not assign the IP address).
and there is another method that may detect another DHCP server on the network: Capture the WAN/LAN traffic and examine it with Wireshark. When a device is powered on, it will send a DHCP discover broadcast (to the MAC address FF:FF:FF:FF:FF:FF). The DHCP server will respond with a DHCP offer packet to the MAC address that the broadcast came from. This will contain the IP address of the DHCP server. Then, the device will respond with a request and finally an acknowledge from the server. This process is explained here:
https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#Operation
This should work as long as the two devices are not physically separated from the Orbi, such as on the same gigabit switch which has created tables showing which switch port every MAC address can be found on.
good catch, yes was so frustrated i didn't even notice i dropped the '1'. indeed... orbi is at 192.168.1.1, and my reserved range is 192.168.1.2 to 192.168.1.9. Dynamic starts at x.x.x.10.
i'll give the test a go. Now I'm super curious what else could be handing out IP addresses?? Cannot imagine what else has a DHCP server?!?
jimslade wrote:i'll give the test a go. Now I'm super curious what else could be handing out IP addresses?? Cannot imagine what else has a DHCP server?!?
It is 99.999% certain that the Orbi is not assigning IP addresses that begin with anything besides 192.168.1.
So, either:
- devices are configured with static IP's that begin with 172, or
- some other DHCP server is giving out these addresses
You would probably remember assigning static IP's, so my money is on another DHCP server. Likely culprits include NAS servers and media devices. Some smart speaker systems attempt to network themselves.
I positively love capturing packets and looking at them with Wireshark, which puts me squarely in the uber nerd category.
Another simplistic question is, "what has been added to the network since things were fine?"
