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...
Ok, just checking and trying to understand your configuration.
Yes seems like the Orbi is havning problems with the modem and possible modem changes.
Something to try, can you set up a static IP address using the public IP address the Orbi is getting from the modem pass thru? Instead of using Dynamic DHCP try Static Mode on the WAN port. Normally this shouldn't be needed and it would normally required having the ISP give you static IP address. Something you might ask the ISP about so the public IP address doesn't change. However this maybe a problem with the orbi router and could be just faulty as others have modems with pass thru and havn't expressed this kind of problem with there Orbi. Something I would file a ticket here and get more help on and ask about an RMA:
https://www.netgear.com/mynetgear/registration/login.aspx
RMA would reveal if the problem was the Orbi you have now or something in FW that doesn't like your particular modem combo unit.
garrettg84 wrote:
I guess nobody read my actual post. I said *public ip* as in non-rfc1918 or other reserved IP space. There is no double NAT. The ISP calls bridge mode 'pass through'. I have no access to the modem itself other than to view its connectivity status (ISP locks us out) - and that is only while I've been given an RFC 1918 non-public IP before it connects and turns into pass through (bridge) mode.
TLDR - No double NAT. No actual IP conflict. Orbi loses its mind.
This issue has been present in all versions of the firmware I've touched (at least 2 updates I can remember off the top of my head besides the firmware it came with out of the box). I simply need the ability to turn of this nanny ip conflict detection service. I don't want it. It breaks my device and incorrectly detects conflicts when there are none in actuality. Everything else works swimmingly. Thinking about it, statically assigning the IP address will probably prevent the thing from going into stupid mode. I'll still be stuck with a bad connection monthly that I'll have to intervene and change it to another IP.
To get an actual static IP from the ISP I've got to upgrade to business class. This doubles my price, cuts my bandwidth in half, but garantees the bandwidth alotment - of which I've never had a problem. This is not a solution.
The product needs to be fixed. The ability to disable a service that causes breakage is what is necessary. If I can't get some support from Netgear on the idea, I'll simply change my positive Amazon reviews to something negative and move to another vendor that won't lose its mind monthly.
So, the Orbi is going crazy once a month (a) because the ISP is literally "restarting" the modem, and (b) the ISP has put the modem in Bridge Mode and the user cannot take it out?
Wow. I did not realize that ISP's were resetting our modems every month, and the modem could be giving out goofy temporary DHCP assignments. (I had thought that when the modem was resetting it didn't talk to the LAN side at all.) My modem's DHCP lease lasts one hour, so the ISP has multiple opportunities to change the public IP every day. I guess the reason my Orbi doesn't go crazy is that I am not in "Bridge Mode."
My Orbi also gets a DHCP lease good for one hour, so I would think that in (30 minutes, correct?) the Orbi would ask to renew the lease, get the new one, and things would straighten out? Or, does the modem in Bridged Mode give that temporary IP out with a longer lease?
So, I am wondering what issue is going to push me into changing to Bridge Mode? (I am not eager to fall into a monthly recurring nightmare.) Is it VPN? Port forwarding? Performance?
Do you have a prior router handy by chance to put in place of the Orbi? If so, might check this to see if same thing happens with that router.
I would open up a support ticket with NG and start some dialog with support in mean time.
garrettg84 wrote:
This issue has been present in all versions of the firmware I've touched (at least 2 updates I can remember off the top of my head besides the firmware it came with out of the box). I simply need the ability to turn of this nanny ip conflict detection service. I don't want it. It breaks my device and incorrectly detects conflicts when there are none in actuality. Everything else works swimmingly. Thinking about it, statically assigning the IP address will probably prevent the thing from going into stupid mode. I'll still be stuck with a bad connection monthly that I'll have to intervene and change it to another IP.
To get an actual static IP from the ISP I've got to upgrade to business class. This doubles my price, cuts my bandwidth in half, but garantees the bandwidth alotment - of which I've never had a problem. This is not a solution.
The product needs to be fixed. The ability to disable a service that causes breakage is what is necessary. If I can't get some support from Netgear on the idea, I'll simply change my positive Amazon reviews to something negative and move to another vendor that won't lose its mind monthly.None of my prior routers had issues with this behavior which has been the same for the past 4 years I've lived in the are and had the same service provider. They were all running DD-WRT or similar distributions of linux. Unfortunately none of them have appropriately simple meshing capabilities (at least not at the time of my purchase) or control over multiple 802.11AC radios I could create my own mesh with. I've been dealing with these mixups for almost a year with one reset per month while getting a new DHCP address with the Orbi.
Something to setup while you start some dialog with NG, setup one of your other routers, just disable wifi on this router. Connect the Orbi in configured for AP mode to the prior router and run this configuration.
garrettg84 wrote:
None of my prior routers had issues with this behavior which has been the same for the past 4 years I've lived in the are and had the same service provider. They were all running DD-WRT or similar distributions of linux. Unfortunately none of them have appropriately simple meshing capabilities (at least not at the time of my purchase) or control over multiple 802.11AC radios I could create my own mesh with. I've been dealing with these mixups for almost a year with one reset per month while getting a new DHCP address with the Orbi.
