NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Disable auto change IP address
I've seen similar posts about a way to disable the auto change IP address before. They've been brushed off. The 'answers' and 'solutions' are wrong. There is an issue with the product. Every month wh...
garrettg84 wrote:
I've seen similar posts about a way to disable the auto change IP address before. They've been brushed off. The 'answers' and 'solutions' are wrong. There is an issue with the product. Every month when my ISP renews my IP address, the Orbi loses its mind. It gets stuck in the IP address conflict loop. I literally have to chase it between the 192.168.0.1, 172.16.0.1, 10.0.0.1, and other random addresses within each of the ranges. Once I manually set it (provided it doesn't hop again before I can submit) to the address I prefer, 10.99.99.1, it stops hopping and magically no longer detects a conflict.
No, it isn't conflicting with my ISP. How do I know? I set up a TAP and ran some PCAPs while unplugging and re-plugging in the cable modem. The interim range is always 192.168.100.x while it is waiting for DHCP to pull my public address. No, that never, not once, not ever conflicts with 10.99.99.1. I need to disable this feature or I'm going to have to throw this $600 (router plus multiple satellites) into the garbage and pick a superior competitor that doesn't lose its mind monthly.
This is total crap. Whatever method you are using to detect conflict is obviously failing.
Orbi has a "feature" designed to make the router "easy to install." If the Orbi detects that the WAN has a private IP that overlaps with the LAN subnet it will automatically switch the LAN subnet to another range. If it's switching when there's no overlap, it sounds like this feature might have a bug. The bug would rarely be seen, except that some cable modems hand out private IPs when the connection to the ISP goes down.
What IP address and subnet mask are you using on the Orbi LAN?
Does the Orbi not return to normal if you leave it alone?
In any case, this sounds like an issue with your ISP as well. If the modem is handing out private IPs it indicates the cable connection is down. The connection shouldn't go down every time they change your public IP.
st_shaw wrote:
The bug would rarely be seen, except that some cable modems hand out private IPs when the connection to the ISP goes down.
This sort of thing, erratic local IP addresses, can also happen if a modem goes down and boots so slowly that if has not made an internet connection before the router kicks in.
If the router can't see the modem, it goes its own sweet way when it comes to selecting an IP address.
In my case, it was when recovering from power cuts that I hit this brick wall. The local network failed to connect to the internet.
This is probably not related to what is going on here, but it does illustrate that subtle interactions between devices on a network can throw things into a tizzy. It may have nothing to do with Netgear's evil firmware.
I agree,
garrettg84, I think that you can easily solve your issue by keeping the private address on the ISP modem so the interface to Orbi keeps always a private address..
Using bridge (passthrough) in the modem seems not working for you since the modem will -momentarily- change to private address when it looses the internet connection and then gets back the public IP address which confuses Orbi.
If you have access to your modem (or if the ISP can help you with that) then I suggest to remove the passthrough mode and instead use DMZ forwarding. This way the modem will keep the private address network and the DMZ forwarding will take care of the double NAT.
ekhalil wrote:
I agree,
garrettg84, I think that you can easily solve your issue by keeping the private address on the ISP modem so the interface to Orbi keeps always a private address..
Using bridge (passthrough) in the modem seems not working for you since the modem will -momentarily- change to private address when it looses the internet connection and then gets back the public IP address which confuses Orbi.
If you have access to your modem (or if the ISP can help you with that) then I suggest to remove the passthrough mode and instead use DMZ forwarding. This way the modem will keep the private address network and the DMZ forwarding will take care of the double NAT.
I don't have the ability to control inbound ports because the ISP modem is locked down. This is not a solution. I don't need to dumb down my network and configurability because the Orbi is falsely detecting an IP conflict. I will simply get another vendor's product that does not have these rediculous issues in a feature I don't want or need.
