NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR40 ORBI assigning IP out of range!
ORBI RBR40 is behaving very oddly. IP Range is set to 192.168.0.x I lost internet to my wired ethernet PC. But was able to successfully connect same PC via WiFi. Checked IP Table and found...
Interesting...
This morning I restarted the router and both satelites ...and for the moment everything is operating fine. Let's see if it stays stable.
The PC now has both wired ethernet and wifi turned on... I'll keep an eye out today to see if that ethernet connection bugs out, in which case my suspicion is that something has gone wrong with the Orbi's ethernet outputs.
I rolled back firmware to V2.6.1.36 just in case.
If I catch the Orbi misbehaving (ie, not assigning proper IP addresses to hardwired devices) would you say that it's a firmware or a hardware issue?
RedCab wrote:If I catch the Orbi misbehaving (ie, not assigning proper IP addresses to hardwired devices) would you say that it's a firmware or a hardware issue?
Sorry I was not clear. The Orbi did not "assign" that private IP to the ethernet port. The computer made up that IP itself because it did not get an IP from the Orbi. The problem is entirely within the Windows 10 computer. (My Windows 10 laptop started doing that and I am embarassed that thus far I have not resolved the issue.)
If every device but one is working correctly, then there must be a problem with the router? - NOT.
I wasn't clear either, sorry.
I wrote about the problem with the PC as example because it provided the most diagnostic info.
The problem also is happening (when it does happen) with other devices downstream from the Orbi's ethernet outputs. For example one of those outputs goes to a switch which supplies my video streaming devices. All of them were unable to reach internet while that issue with the PC was going on.
SO... it's on the Orbi side of things, right? Would you agree the Orbi isn't registering hardwired ethernet connections, ie, not assigning IP address to those, in turn causing "no internet" at those various devices?
The wifi connections off the Orbi appear to be uneffected, at least I haven't observed an issue with those (yet).
I have captured LAN packets on my test Orbi two times. Both clearly show my Windows 10 PC using DHCP to request an IP address and the Orbi responding with an IP request.
I will do another experiment tomorrow with more devices to see if there is a difference between how the Windows 10 PC does DHCP and how other devices do it. Sorry to take so long.
Performed another experiment.
Began WAN/LAN packet capture on Orbi debug page.
Closed lid on laptop (put to sleep).
Plugged power into Nest Mini. Took a minute, but it came alive and told me the time. (Hey Google, what time is it?)
Connected Linux laptop to Orbi WiFi. Entered password. Opened up web pages. Connection working.
Opened lid on Win 10 laptop. Woke up. Entered password. "Unidentified Network." Funny round icon.
Waited about 90 seconds.
Started Network troubleshooter. Selected ethernet port.
Now network shows as ORBI80 (which is what it is). Laptop has IP address.
Logged into Orbi debug page and saved debug log.
Use Wireshark to display DHCP packets.
Clearly shows the Nest Mini and the Linux laptop doing exactly what the DHCP protocol says to do:
Device broadcasts "Discover"
DHCP server responds "Offer"
Device sends "Request"
DHCP responds "ACK"
The Win 10 laptop, however did NOT follow the protocol:
Laptop broadcasts "Discover"
DHCP server responds "Offer"
Laptop broadcasts "Discover"
DHCP server responds "Offer"
This went on for 114 seconds until I the Network troubleshooter kicked in.
Finally, the Win 10 laptop followed the protocol. Discover->Offer->Request->ACK.
I remain convinced that although there are definite issues with the way Netgear handled DHCP in the context of IP assignments, the DHCP process follows the protocol. My Windows 10 laptop does not. Why? No idea. It's a major pain in the nether region. I have searched for "Unidentified network" and got nothing helpful.