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...
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.
garrettg84 wrote:
I will simply get another vendor's product that does not have these rediculous issues in a feature I don't want or need.
A word of warning, all routers are likely to show similar behaviour if you insist on slapping them behind another router.
By the way, a quick check of a manual for the Ubee DDW36C suggests that it has advice on setting it up in bridge mode.
Ubee DDW36C Advanced Wireless Gateway - cloudfront.net
You may need those instructions with the next router you try to shoehorn on to your network.
I guess nobody reads any of the above posts before posting. I have no control over my cable modem. I have to call my ISP to get them to put it in 'pass through' (Bridge mode). I don't need to, nor can I, configure my cable modem.
I need the Orbi to kill the IP conflict service. It is not functioning properly. My internal network subnet is 10.99.99.0/24. The external subnet is either a public IP address during normal operation, or 192.168.100.0/24 during connecting/reset operations. There is never an actual conflict. These subnets do not overlap. There is a problem with the service.I don't have a router slapped behind a router. Stop being inflamitory. Read the posts. Offer something useful, or simply don't comment. It is very easy.