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...
randomousity wrote:
garrettg84 wrote:The mode selected by the ISP is bridged mode (even though they call it "pass through"). Even if this were the case, I would simply have no connectivity. I have connectivity just fine. This is another red herring/distraction. The Orbi is stuck in an address conflict loop every time my cable modem resets. It detects a conflict when there is no conflict.
If the ISP uses the wrong terminology, I can't do anything about that.
But how do you know they're actually using bridge mode? How do you know they're actually using bridge and just calling it passthrough, rather than actually using passthrough and calling it by the proper name? I bet they're actually using passthrough mode, because in bridge mode, there would be no DHCP server at all on the Ubee, so nothing would be issued a 192.18.100.0/24 address at all in the first place. The Ubee would be transparent to your Orbi, which, for practical purposes, would consider itself to be directly connected to your ISP, with whatever public IP your ISP assigns you.
I can see the setting in the diagnostics page even though I have no permissions to change it. It is in bridged mode. The connection works until the modem resets. I have connectivity. I would have no connectivity if this were the case. Under normal circusmstances, I'd love to know how you feel that even if it is in actual pass through mode the Orbi would constantly detect IP conflicts - but only on connection resets. Today, I know it can't and I don't need to wait for your answer. This is a red herring. It deserves no more attention.
The Orbi has a flawed method for detecting IP conflicts. I've tapped the connection and watched the traffic. I am 100% sure the Orbi is detecting an IP conflict when there is none. I watch the DHCP request. I see the DHCP offer. I then watch it continue to make DHCP requests every 30-45 seconds. I assume it does this every time it sets the internal LAN to a new subnet.
It is possible I have a malfunctioning unit. I've submitted a ticket to Net Gear. I'm still waiting on a response.
garrettg84 I have a few questions for you:
- When you look at the Ubee's config in diagnostic mode, the coax is physically disconnected, right?
- When the coax is physically connected (i.e. when the Ubee is in operational, rather than diagnostic, mode), you can't view any settings in the Ubee at all, right?
- Given Q1 & Q2, assuming they're both "yes," it's possible that when you look, it's in bridge mode, and when it's in passthrough mode, you're unable to look, right?
- Given Q3, it's possible you are incorrectly assuming the Ubee is always in bridge mode, rather than only sometimes in bridge mode (when it's in diagnostic mode), and sometimes in passthrough mode (when it's operational), right?
- Given Q4, it's possible that when the ISP says your Ubee is in passthrough mode, that that's what they actually, literally, mean, and not that they are using incorrect terminology, right?
- What does "bridge mode" mean?
- When a device (e.g., your Ubee) is put in "bridge mode," that means it's functioning at which layer of the OSI model?
- When a device has an IP address, and functions as a DHCP server, now which layer of the OSI model is it on?
Your Ubee has a reset button on the back that you can push with a paper clip. If you disconnect the coax cable, reset the Ubee, and then connect in diagnostic mode, you should be able to change the settings, because it won't have been locked down by your ISP yet. However, it probably won't detect the coax unless you power cycle it, at which point it will pull its configuration from the ISP, most likely overriding your changes. But hey, give it a try. It can't hurt.
I've tapped the connection and watched the traffic. I am 100% sure the Orbi is detecting an IP conflict when there is none. I watch the DHCP request. I see the DHCP offer. I then watch it continue to make DHCP requests every 30-45 seconds. I assume it does this every time it sets the internal LAN to a new subnet.
Ok, I'll take your word for it. But, which interface were you looking at (I assume the WAN interface, but just checking), and how do you know what the conflict is? I believe you when you say there's a conflict, but there are multiple possible conflicts. As you've said, it doesn't make ansy sense for 192.18.100.0/24 to conflict with 10.99.99.0/24, so why do you assume this is the actual source of conflict, as opposed to something else? If your ISP assigns you, say, 1.2.3.4, and your Ubee gets that address, the Orbi also getting that address would be a conflict, right? Two devices with the same IP on the same network is a conflict, right? So, if that's what's hapening, the Orbi would request a new IP, and the ISP might say, here's the only IP you're getting from us, and this cycle could continue indefinitely, right?