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?"
jimslade wrote:
Ooma still shows at 172.27.35.1 in the Orbi device list. I'm guessing that IP is set on the device side (I'll have to go connect to it again to see how that's set). Assuming that's true, I don't know what happens to the service if I try to change that or even if that is possible.
Where does the 192.168.1.8 IP address come from? Does it appear in the Orbi Attached Devices list?
p.s. Which Ooma is this
- Ooma Tele White, or
- Ooma Tele Air
The Ooma is working, correct?
CrimpOn wrote:Where does the 192.168.1.8 IP address come from? Does it appear in the Orbi Attached Devices list?
p.s. Which Ooma is this
- Ooma Tele White, or
- Ooma Tele Air
The Ooma is working, correct?
I set a static IP rule on Orbi to assign 192.168.1.8 to Ooma's mac address. I'm guessing Ooma is specifying it's own IP (172.27.35.1), which i'm thinking is 'winning' over Orbi's assignment as Ooma is dictating its IP on the client side (no assignment from Orbi).
192.168.1.8 doesn't show anywhere that I see.... Ooma shows up as 172.27.35.1.
I'm using an Ooma Telo. Yes, Ooma is working fine.
I can't ping 172.27.35.1... I'm a networking noob, but I'm guessing that I need to be in the 172 range to 'see' Ooma? Again, I don't understand networking but I find it interesting that Ooma doesn't really care if it is not in range works just fine, but I can't connect to ooma. I guess I have to be on Ooma's 'subnet' to see/ping Ooma.
This is connected the regular way, correct? (Not one of the alternare method on page 2)
https://support.ooma.com/assets/pdfs/Ooma-Telo2-QSG_EN%20700-0127-400.pdf
Yes, no device in the regular 192.168.1.x subnet can contact a device with a 172. IP address, which is why I do not understand how this is working at all. It should not be able to reach the interent.
So, a web page aimed at http://192.168.1.8 does not connect?
Could you make a screen shot of that attempt to set up a static router to the Ooma?
Want to check on the subnet mask used. For a single IP address, it should be 255.255.255.255
Also, the Help for static routes mentions using the IP address of a router on the network. So, it is not entirely clear to me what happens if the host for the static route is not a router. (My ignornance knows no bounds!)
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! :) .