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...
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?"
Think I have answered my own question. I set up a static route to 123.123.123.123 to point to my printer, which definitely responds to ICMP (ping). No Joy. The printer does not recognize 123.123.123.123, so it does not respond.
Sorry, should have tested before posting.
I
Well CrimpOn your ignorance is exceeded by my ignorance.
Yes, Ooma is installed behind Orbi on my LAN with Orbi as the router aka 'standard'
Two mistakes by me:
1) I input subnet mask as 255.255.255.0. You said use 255.255.255.255 so I changed to that and the static rule saved properly (as 192.168.1.8 -> 172.27.35.1). Though looks like I don't need a static route because of #2 next.
2) I'd inadvertently plugged ethernet cable into the home port instead of the ethernet port on Ooma. This explains why I was seeing 172.27.35.1 as the IP address.... guessing that is Ooma's LAN address (I think?).
Now I see the Ooma device on Orbi as:
| IP Address | 192.168.1.82 |
| MAC Address | 00:18:61:4B:39:B9 |
I can ping 192.168.1.82 just fine.
I also see that the only way to reach Ooma's management interface is via Ooma's LAN address. I need to be physically plugged into the LAN/'HOME' port to reach the management interface. And since I turned off DHCP for that, I'm assuming that the next time manually I plug into the LAN interface I need to configure a static IP on my computer, because I won't be getting an IP from Ooma (no DHCP! :) .