Disable auto change IP address

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=desktop

This 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/router

MFR: 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.

---

---

garrettg84 wrote:

---

...
MFR: Ubee

Model: DDW36C

...

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.

---

This is the cumbersome local "management" access to an non-connected, non-configured cable modem (or cable router) before receiving the configuration from the TV Internet operator. These cable modems are intended to be run 24*7, and are typically connected to some 99.9x% to the cable TV provider network. And this mode is virtually invisible. You do not - never - power-off that cable modem. Should it happen that the cable modem does loose connection to the cable TV network or it does reboot at that point randomly, talk to the TV network operator - this should not happen regularly.

---

garrettg84 wrote:

---

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.

---

Now when you connect any system - no matter an Orbi router, another vendor router, or simply a computer direct to the cable modem, you should be able to get always the public IP address.

Consumer and many business class routers simply run a DHCP client, and put the the address assigned to the Internet/WAN interface.

---

garrettg84 wrote:

---

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.

---

Here again, the router has to accept the new assigned - it does not know of this assigned config is coming from the cable modem local management mode, or from the cable ISP DHCP. Some ISP disconnect and force a re-connection assigning a new IPv4 address every 24 hours, some every week, some every month, ... some randomly or almost never. Either case, the router has to accept this change, and can't do anything against. 

---

garrettg84 wrote:

---

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?)

---

Orbi does default to the 192.168.1.0/24 for the LAN. Like most newer Netgear routers. 

There is nothing that stops you form changing the LAN config to use say 10.99.99.0/24 with the Orbi LAN being on 10.99.99.1, and adopt the DHCP pool accordingly (happens automatically I'd expect). Essentially, this is what I would suggest to do - and I show you below, why.

---

garrettg84 wrote:

---

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?" 

---

Up to here we can only guess - in the flood of information I can't see what really happens. The Netgear router have a "smart-a**" functionality - if they see certain private LAN IP on the WAN/Internet side, they go and (silently!) reconfigure the LAN to be on a very different subnetwork (unless it is already). Now I know for sure this will happen if the WAN/Internet interface would receive a 192.168.1.0/24 address. But the lazy implementation might go and change if it does get a 192.168.100.0/24 address, too. And then the router LAN will go to 10.0.0.1 (either a /24 [25.255.255.0] or a /8 [255.0.0.0] subnet) - HAVOC perfect. While that's not correct - well welcome to Netgear!

When you head to the LAN config on 10.99.99.0/24 it's less risk that the "dumb-a**" protection does jump in again.

Hope this does clarify.