NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DHCP issues after Orbi in AP Mode RBK50 reboot
netgear Something is wrong with DHCP after a reboot of my main router (UBEE), & the way it interacts with the Orbi system. I have an UBEE modem which also acts as router with DHCP provided through my ISP Optimum (Altice). I have the Orbi system setup in AP mode. Everything works great once I follow this order. First, having the UBEE fully restartarted / online. Then 1 by 1 replugging everything else in. Next, the main Satellite or Router (AP Mode). Then with the main satelite on for a few minutes while the other satellites are off / unplugged. I go to each additional satelite connected through my ethernet backhaul and plug them back in. This results in the network working fine. The problem is the system just doesn't do this on its own. If I just run a reboot or unplug the UBEE. Nothing goes back online correctly / most devices dont recieve a valid IP. Some devices dont recieve an IP till after I physically do this hard reboot and instead change to the IP 169.254.0.0 or my android devices just say 0.0.0.0... I am finding this very similar to a problem being described on reddit with subject title Possible DHCP issue with Orbi after reboot?
6 Replies
computersteve wrote:First, having the UBEE fully restartarted / online. Then 1 by 1 replugging everything else in. Next, the main Satellite or Router (AP Mode).
It would help to know what "replugged" means. (ethernet cord pulled and reinserted or powered off and back on).
If devices are restarted (powered off/on) when the Orbi is not connected to the UBEE, then they should all attempt to get an IP using DHCP, fail to get one, and then set themselves to their "default" 169.x.x.x address.
When I restart my modem, or even restart my Orbi, I never power off any devices. Since you are able to reach the ISP tech support line, it would be useful to know what the UBEE "DHCP Lease Time" is. The Orbi default, for example is one day (86,400 seconds). Devices are supposed to begin asking to renew their IP address when half of the lease time remains and keep doing so periodically until the lease expires. If the UBEE DHCP lease is very (very ) short, then devices could possibly "time out" on the renewal while the Altice is powered off. If the UBEE is simply being "restarted", this seems a remote possibility.
I believe the reddit post mention was about Orbi in router mode, not AP mode.
So, I have no explanation, only questions.
The problem is it doesn't recieve IPs after the UBEE reboots.. If I run a wireshark it says that its then sending request to 192.168.1.255 meanwhile my gateway (UBEE) is 192.168.1.1.. If I reboot everything it then works and it resumes recieving IP's from 192.168.1.1
computersteve wrote:The problem is it doesn't recieve IPs after the UBEE reboots.. If I run a wireshark it says that its then sending request to 192.168.1.255 meanwhile my gateway (UBEE) is 192.168.1.1.. If I reboot everything it then works and it resumes recieving IP's from 192.168.1.1
I have lost track of what "it" is. Is Wireshark recording packets from the machine that Wireshark is running on?
Wikipedia explains DHCP requests as starting with a "broadcast" to IP 255.255.255.255 and then waiting for the first DHCP server to respond. With the Orbi in AP mode, that should be the UBEE.
What happens if you set a STATIC IP address on the RBR in AP mode thats outside of the modems IP address pool?
computersteve wrote:netgear Something is wrong with DHCP after a reboot of my main router (UBEE), & the way it interacts with the Orbi system. I have an UBEE modem which also acts as router with DHCP provided through my ISP Optimum (Altice). I have the Orbi system setup in AP mode. Everything works great once I follow this order. First, having the UBEE fully restartarted / online. Then 1 by 1 replugging everything else in. Next, the main Satellite or Router (AP Mode). Then with the main satelite on for a few minutes while the other satellites are off / unplugged. I go to each additional satelite connected through my ethernet backhaul and plug them back in. This results in the network working fine. The problem is the system just doesn't do this on its own. If I just run a reboot or unplug the UBEE. Nothing goes back online correctly / most devices dont recieve a valid IP. Some devices dont recieve an IP till after I physically do this hard reboot and instead change to the IP 169.254.0.0 or my android devices just say 0.0.0.0... I am finding this very similar to a problem being described on reddit with subject title Possible DHCP issue with Orbi after reboot?
never tried static.. I will try that now and let you know..
So theres a weird IP
127.160.0.2 showing in the device list but then it disapears..
