Disable auto change IP address

I continue to be amazed.  garrettg64's Ubee DDW36C User Guide has that section 6.7 that describes "Passthrough", although I am confused by the description.  It looks like up to 32 MAC addresses get "added" to a table which "Displays the MAC addresses to be blocked."  So, are these MAC addresses "passed through", or are they "blocked"?  And, "Input Host" refers to???  (the modem?  the Orbi?  Spectrum?)

My Ubee DVW36CB (voice, with a battery slot which Time Warner left empty) User Guide does not have section 6.7.  Nada.  So, that means that my Ubee cannot be set to Bridge Mode?

---

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.

---

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.

---

CrimpOn wrote:

I continue to be amazed.  garrettg64's Ubee DDW36C User Guide has that section 6.7 that describes "Passthrough", although I am confused by the description.  It looks like up to 32 MAC addresses get "added" to a table which "Displays the MAC addresses to be blocked."  So, are these MAC addresses "passed through", or are they "blocked"?  And, "Input Host" refers to???  (the modem?  the Orbi?  Spectrum?)

 

My Ubee DVW36CB (voice, with a battery slot which Time Warner left empty) User Guide does not have section 6.7.  Nada.  So, that means that my Ubee cannot be set to Bridge Mode?

---

Ok, here's how I interpret that: There's a table which can contain up to 32 MAC addresses. Any addresses added to that table are blocked from being intercepted and managed by the Ubee. The are, instead, passed through the Ubee to the ISP, so the ISP can manage them (which generally just means that a device configured to use DHCP will send out an ARP broadcast requesting to be assigned an IP address by the DHCP server, and instead of the Ubee responding, the Ubee is blocked from responding, and being told to pass the ARP message through to the ISP, for the ISP to respond to instead), as though they (your network device and the ISP) were directly connected without the Ubee as an intermediary. And I think "the input host’s MAC addres" also has awkward wording, but means "the MAC address of the host which you, the user, have input."

Basically, the descriptions are garbage, but it makes perfect sense if you look directly at the (image of) the config page.

Pass Through MAC addresses [gives example of what a MAC looks like]

[field to input your specified host's MAC] [button to add the MAC, which has been input, to the table]

[table of added MACs, displayed in list form] Addresses entered [count of MACs entered into the table]/32

[remove single selected MAC from the table button] [clear entire table button]

---

---

randomousity wrote:

---

---

Ok, here's how I interpret that: There's a table which can contain up to 32 MAC addresses. Any addresses added to that table are blocked from being intercepted and managed by the Ubee. The are, instead, passed through the Ubee to the ISP, so the ISP can manage them (which generally just means that a device configured to use DHCP will send out an ARP broadcast requesting to be assigned an IP address by the DHCP server, and instead of the Ubee responding, the Ubee is blocked from responding, and being told to pass the ARP message through to the ISP, for the ISP to respond to instead), as though they (your network device and the ISP) were directly connected without the Ubee as an intermediary. And I think "the input host’s MAC addres" also has awkward wording, but means "the MAC address of the host which you, the user, have input."

---

Maybe it's just as well that MY Ubee modem doesn't have this feature.  If this feature really operates like this, then it certainly is NOT what I think of as bridge mode. The ISP has no idea what router the user is going to connect to the modem, and the user is able to change home routers at will.  In bridge mode, the user cannot get into the Ubee to input a MAC address for the ISP, and I have never heard anyone on this forum talk about putting MAC addresses into their modem.  Even if it was intended to run the other direction and the ISP was supposed to put in the MAC addresses of up to 32 hosts that might communicate with the modem, that would unmanagable in the long run.  They can't go around updating tables in every modem whenever they add or swap out equipment.

I think we would all agree that when we put our Orbi in "router mode", it should be impossible for anything except a logged in administrator to change the mode to something else or create a VLAN Bridge.  If we have set the LAN IP to 10.99.99.1, then the Orbi should not change it to anything else unless it saw 10.99.99.1 on the WAN side.  If garrettg64's router suddenly changes its LAN address to a public address, it has gone wack-o.  He did a reset to factory a couple of days ago, and will learn in just under four weeks if the problem still exists.

It would be interesting if some community member has a Ubee DDW32C in bridge modem on Spectrum and has "no problems."

garrettg84 I have a few questions for you:

1. When you look at the Ubee's config in diagnostic mode, the coax is physically disconnected, right?
2. 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?
3. 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?
4. 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?
5. 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?
6. What does "bridge mode" mean?
7. When a device (e.g., your Ubee) is put in "bridge mode," that means it's functioning at which layer of the OSI model?
8. 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?

One way to tell if the ISP modem IS bridged, the IP address should be a public IP address ON the Orbi's WAN side. If your not seeing a ##.##.###.### kind of address on it's WAN port, and you see anything else like a 192, 172 or a 10 IP adderss, the ISP modem is not bridged.

---

CrimpOn wrote:

---

---

randomousity wrote:

---

---

Ok, here's how I interpret that: There's a table which can contain up to 32 MAC addresses. Any addresses added to that table are blocked from being intercepted and managed by the Ubee. The are, instead, passed through the Ubee to the ISP, so the ISP can manage them (which generally just means that a device configured to use DHCP will send out an ARP broadcast requesting to be assigned an IP address by the DHCP server, and instead of the Ubee responding, the Ubee is blocked from responding, and being told to pass the ARP message through to the ISP, for the ISP to respond to instead), as though they (your network device and the ISP) were directly connected without the Ubee as an intermediary. And I think "the input host’s MAC addres" also has awkward wording, but means "the MAC address of the host which you, the user, have input."

---

Maybe it's just as well that MY Ubee modem doesn't have this feature.  If this feature really operates like this, then it certainly is NOT what I think of as bridge mode. The ISP has no idea what router the user is going to connect to the modem, and the user is able to change home routers at will.  In bridge mode, the user cannot get into the Ubee to input a MAC address for the ISP, and I have never heard anyone on this forum talk about putting MAC addresses into their modem.  Even if it was intended to run the other direction and the ISP was supposed to put in the MAC addresses of up to 32 hosts that might communicate with the modem, that would unmanagable in the long run.  They can't go around updating tables in every modem whenever they add or swap out equipment.

 

I think we would all agree that when we put our Orbi in "router mode", it should be impossible for anything except a logged in administrator to change the mode to something else or create a VLAN Bridge.  If we have set the LAN IP to 10.99.99.1, then the Orbi should not change it to anything else unless it saw 10.99.99.1 on the WAN side.  If garrettg64's router suddenly changes its LAN address to a public address, it has gone wack-o.  He did a reset to factory a couple of days ago, and will learn in just under four weeks if the problem still exists.

 

It would be interesting if some community member has a Ubee DDW32C in bridge modem on Spectrum and has "no problems."

---

Have you tried the manual reload of FW, factory reset then setup from scratch? 

Besure to have NG capture your logs from the Orbi router as well for there review. Hoping the logs may say something. 

---

garrettg84 wrote:

---

It is possible I have a malfunctioning unit. I've submitted a ticket to Net Gear. I'm still waiting on a response.

---

Any progess on this? I hope NG support is looking into this. 

---

garrettg84 wrote:

---

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.

---