NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DHCP / IP Issues with Sky Broadband (UK FTTC DSL) Hub
Hello all. Hoping you might be able to advise me on this issue please? I recently received an updated modem/router from my broadband provider. It was supposedly the newer/better model and it ...
n_sonic wrote:On it's own, the new modem/router (with it's wi-fi off) dishes out 192.168.0.x addresses and a "router" address of192.168.0.1 via its ethernet ports.
However, the moment the Orbi is connected to this new modem/router - everything starts getting 192.168.1.x addresses a "router" address of 192.168.0.250. This causes all internet connectivity to fail and neither the modem/router or Orbi are accessible via their browser-based admin interfaces anymore.
This happens when anything is connected to the new router, or just when the Orbi is connected?
The broadband supplier has no suggestions?
Good question. I've only tried plugging the Orbi in so far, so I can't answer that. I have a Hue hub and a Homebridge that I can try to see if it causes similar behaviour.
I've not reached out to the broadband supplier yet. I've been holding off, hoping to get some ideas from the support community first :)
I will try a couple of the other suggestions (static IP outside the DHCP range) and then try a full factory reset.
Can you explain how you discovered the changing IP assignments?
Ordinarily, the first recommendation is to connect a PC directly to the modem/router with an ethernet cable and verify that "it works".
(I was thrown by the statement that the modem/router's WiFi is off.)
I would want to log into the modem/router and look at their version of Attached Devices to see what it reports about everything connected and its own LAN IP address.
"Can you explain how you discovered the changing IP assignments? Ordinarily, the first recommendation is to connect a PC directly to the modem/router with an ethernet cable and verify that "it works". (I was thrown by the statement that the modem/router's WiFi is off.)"
Very happy to :)
So, with the Orbi disconnected and wi-fi turned off on the modem/router, I connected a MacBook Pro (wi-fi off) to it directly via ethernet.
When it was just the laptop connected to the modem/router - it was getting the correct 0.x address and the right router address.
I then disconnected the laptop and re-connected the Orbi to the modem/router and gave it a moment to do its thing.
Then I did three more tests with the MacBook Pro.
The first test was with wi-fi off on the MBP. I connected it via ethernet into the modem/router and observed that it was now getting the 1.x address and the wrong router address.
The second test was with wi-fi off again on the MBP. I connected the MBP to the Orbi via ethernet. Again, 1.x addresses and the wrong router address was being assigned.
The final test was to unplug the MBP ethernet and then connect it to the Orbi via wi-fi. Again, the 1.x address and wrong router address was assigned.
So, long story short - as soon as the Orbi was plugged in to the modem/router - everything starts getting 1.x addresses and the wrong router address (no matter where it's connected or how...)
"I would want to log into the modem/router and look at their version of Attached Devices to see what it reports about everything connected and its own LAN IP address."
Great idea. I'll do some more testing tomorrow (as I've got some updated firmware now) and will check what it says.
Thanks again!