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 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.
83 Replies
What FW is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?
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.
FURRYe38 wrote:
What FW is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?Orbi
Model: RBR50
Router Firmware Version: V2.2.1.210
Cable Modem/routerMFR: Ubee
Model: DDW36C
Part No: DDW36C1
HW Version: 3.22.1
Cable modem is configured in 'passthrough' mode. Whatever device is connected gets a public IP once uplink/downlink is established.
Before uplink/downlink, 192.168.100.1/24 IP address is assigned to modem. Connected host(s) get 192.168.100.(11-254)/24 IP until uplink/downlink is established.
After uplink/downlink is established, lan link is dropped and brought back up to induce DHCP discover. Public ISP owned IP is handed out via DHCP (stays same for approximately one month) to connected host - only one host can get a public IP, other hosts fail to connect. Orbi router is only connected device.
So the modem is a gateway thus having it's own router built in. Even though IP Pass thru should be working, I believe this depends if the modem is in full gateway mode or if possible, bridged. If gateway mode and using IP pass thru, then I believe the DHCP services are still going on the modem thus maybe giving a 192.168.something address to the Orbi router. And the Orbi is having a hard time with this.
Can you tell us what the Orbi router has for an IP address ON the Advanced Tab status page currently? Is the public IP address ##.##.###.### or a 192.168 something?
If your seeing a 192 address or anything other than the public, this could be the cause.
I would try one fo the following to see if this corrects the bad DHCP detection behavior between the modem and Orbi:
Couple of options,
1. Configure the modem for transparent bridge mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly. If this is possible this would be prefered. If not, go to #2.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ or IP PassThru for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode. I would reserve an IP address ON the modem for the Orbi router. This would help avoid any conflict as well. You can set up a 192.168.0.1 IP address for the LAN side of the Orbi. This is what I use.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, configure AP mode on the Orbi router. https://kb.netgear.com/31218/How-do-I-configure-my-Orbi-router-to-act-as-an-access-point and https://www.youtube.com/watch?v=H7LOcJ8GdDo&app=desktopThis would be a last resort and something to test to see if this helps as well.
garrettg84 wrote:
FURRYe38 wrote:
What FW is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?Orbi
Model: RBR50
Router Firmware Version: V2.2.1.210
Cable Modem/routerMFR: Ubee
Model: DDW36C
Part No: DDW36C1
HW Version: 3.22.1
Cable modem is configured in 'passthrough' mode. Whatever device is connected gets a public IP once uplink/downlink is established.
Before uplink/downlink, 192.168.100.1/24 IP address is assigned to modem. Connected host(s) get 192.168.100.(11-254)/24 IP until uplink/downlink is established.
After uplink/downlink is established, lan link is dropped and brought back up to induce DHCP discover. Public ISP owned IP is handed out via DHCP (stays same for approximately one month) to connected host - only one host can get a public IP, other hosts fail to connect. Orbi router is only connected device.
The model of the ISP modem shows he's in a double NAT condition.
Just need to figure out if he can either bridge the modem or get the IP pass thru or DMZ configured correctly with a reserved IP on the modem for the orbi if the modem can't be bridged.
This discussion has exposed even more of my networking ignorance, and I am so confused. It appears that I do not even understand the problem. i.e. What, exactly, causes garretg84 to go "chasing IP's" every month?"
My modem/router is a ubee DVW32CB. It has been installed for years. My devices appear to do what they are supposed to do. I have PC's, phone, tablets, TiVo, television, Blu-Ray, Vizio soundbar, thermostat, wall plugs, IP cameras, etc. Everything "works". I used the password printed on the ubee label to check the modem settings. Although the "radio" is set to "enabled", both the 2.4G and 5G "primary networks" are set to "disabled" and I cannot detect any WiFi coming from the modem/router. I cannot find a setting called "Passthrough", but on the "Advanced" tab there is a setting called "Primary Network Bridged" which is not enabled. The modem definitely assigns DHCP. Although the modem web interface is at 198.162.100.1, it gives itself 198.162.0.1 and assigns my Orbi 192.168.0.3 (have no idea what happened to "2") So, it is pretty clear that I have a "double NAT."
My Orbi also assigns DHCP in 198.162.1.x and gives itself 198.162.1.1. Frankly, I do not understand what difference it would make if I had chosen 10.99.99.x and given the Orbi 10.99.99.1. What happens on the WAN side is entirely separate from the LAN side. (Or, not?)
So, why does he go through hell every month and I do not? Is it because even with numerous devices, my network use is "dirt simple?" i.e I do not use DDNS, VPN, port forwarding, port triggering, etc. etc.? If I tried any of those things, my "double NAT" would cause me to fail? If I set my ubee modem "Primary Network Bridged" to "enable", would my life to to hell?
There is something that must be obvious to everyone that I just do not understand.
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.
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.
Most cable modems, save the ones that maybe have built in routers that default to 192.168.1.1, most other stand alone cable modems default to 192.168.100.1, this would not conflict with what NG uses as there default address of 192.168.1.1. Of course I don't use modems with routers built in so I have not had chance to experience this kind of issue. For the modems I have used, all stand alone, there isn't any kind of IP conflict in this regard with any of my routers using .0.1 or .1.1. Even if I remove the RF cable.
I presume the only issue here would be if the modem router unit uses a default or falls back to 192.168.1.1 when the RF cable is disconnected and if you have your NG router using same IP address string, then the Orbi would detect this then switch itself to a 10. something IP address pool. Correct?
Looking at the user manual, about 2.5 years old, I see it's default is 192.168.100.1
The DDW36C is pre-configured with the default parameters for Charter Communications
(formerly Time Warner Cable).
Local Port Address: 192.168.100.1
Web Interface: http://192.168.100.1
Operation Mode: NAT Mode
Subnet Mask: 255.255.255.0This shouldn't be a problem...
With his LAN side set to 10.99.99.x, it seems a stretch to think the modem would come up with an IP in that range. I can hardly imagine the trauma of having 100+ devices that want to talk to 10.99.99.1 and suddenly it isn't there any more.
I think you are catching on to why I'm agitated. Regardless of what the modem defaults to, my internal LAN is set to 10.99.99.0/24. This is not any of the known (to me) defaults for any network gear on the planet. But somehow, it is still detecting a conflict and still flipping out my Orbi.
FURRYe38 wrote:
Most cable modems, save the ones that maybe have built in routers that default to 192.168.1.1, most other stand alone cable modems default to 192.168.100.1, this would not conflict with what NG uses as there default address of 192.168.1.1. Of course I don't use modems with routers built in so I have not had chance to experience this kind of issue. For the modems I have used, all stand alone, there isn't any kind of IP conflict in this regard with any of my routers using .0.1 or .1.1. Even if I remove the RF cable.
I presume the only issue here would be if the modem router unit uses a default or falls back to 192.168.1.1 when the RF cable is disconnected and if you have your NG router using same IP address string, then the Orbi would detect this then switch itself to a 10. something IP address pool. Correct?
Ok, so lets try this.
Can you download the Orib v210 router FW for the RBR unit?
https://www.netgear.com/support/product/RBR50.aspx#download
When you get this file, Power OFF the modem. Let it sit there.
Connect up a wired PC and send the v210 FW to the RBR unit and let it process it. After it's processed, hold the back reset button in until the top LED turns AMBER, then let go. Power ON the modem now. After it's ready, walk thru the setup wizard on the RBR and setup the RBR from scratch. Let the wizard detect the modem and complete the setup. When you get to the end, check to see that the RBR should be using 192.168.1.1 for the LAN and if your modem is pass thru or bridged, check the IP address ON the WAN port. IT should be a ##.##.###.###?
Let us know what you find.
Test this further, disconnect the RF cable from the ISP Modem and reboot/power cycle the modem. Check the IP of the orbi...If the default is 192.168.100.1 for the modem, the Orbi should still maintain it's .1.1 address...
I have experienced the same problem (among many others) with the Obri. I have AT&T fiber with Arris modem. I'm about ready to ditch Orbi.
jbofjax wrote:
I have experienced the same problem (among many others) with the Obri. I have AT&T fiber with Arris modem. I'm about ready to ditch Orbi.
Do you have access to your Arris router? Is presume that you already have it in Passthrough mode? There is a setting in the router called "Passthrough DHCP Lease" which specifies how long the host's IP address will be kept private until a WAN address is obtained. Please shorten this time to as short as possible.
Please see page 76 in the manual for Arriss NVG589 as an example here: https://community.arubanetworks.com/aruba/attachments/aruba/unified-wired-wireless-access/26009/1/Motorola%20NVG589%20VDSL2%20Gateway.pdf
- I’ve attached my routers exact info.
It’s in DMZ mode so the orbi’s MAC address is registered in it as a DMZ preset which give the Orbi the public IP. I’m not sure if the setting you mentioned is available for this model as well.
Modem Combo Units:
This would be a double NAT condition which isn't recommended. Couple of options,
1. Configure the modem for transparent bridge mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode. The Orbi will always get a private IP address on this configuration, since the ISP modem can't be bridge and the DHCP disabled, the Orbi will get a private IP address only.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, configure AP mode on the Orbi router. https://kb.netgear.com/31218/How-do-I-configure-my-Orbi-router-to-act-as-an-access-point and https://www.youtube.com/watch?v=H7LOcJ8GdDo&app=desktopI recommend trying option #3...
jbofjax wrote:
I have experienced the same problem (among many others) with the Obri. I have AT&T fiber with Arris modem. I'm about ready to ditch Orbi.
