NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DHCP address reservations had not been respected
I am having similar issues with a RS280 and firmware 1.0.6.16. We recently had an extended power outage that outlasted my UPS. When the power returned, most of the DHCP address reservations had n...
No, I did not perform a factory reset after firmware update. It was annoying enough to put in all my IP reservations the first time. I can't see re-entering all of my network configuration every time Netgear releases a security update.
There is a PoE switch between the router and six of the Ethernet devices (IP cameras) and a hub between the router and two PCs.
Not sure why the ISP modem is relevant as I have turned off its DHCP server. The RS280 assigned IP addresses, just not the correct ones.
DHCP IP address range is 10.0.0.2 - 10.0.0.254
Thanks for the help!
You can save off a router back up configuration prior to performing the factory reset and setup from scratch. Can re-load the back up configuration. I would first test a bit more before applying the back up configuration to ensure your not re-introducing anything in to the mix.
Check with the devices to ensure the devices are configured correctly to get DHCP IP reserved IP addresses.
Do all devices get a random IP address with IP addresses set for reservations on the RS router?
I would test the ethernet PCs directly connected to the router with out being connected to this PoE switch. This could be causing issues. Brand and model# of this PoE switch?
I presume the PoE switch is for the IP cameras?
Brand and model# of the two PCs?
Brand and model# of the ethernet adapters with in these two PCs?
How many devices are connected to the router in total?
Brand and model# of the ISP modem as it is relevant to the configuration and how it interacts with the router. Even if DHCP is disabled. Hard to help you out fully with out know full details here.
Is the modem fully in bridge mode or just DHCP disabled?
Try chaning the DHCP IP address range to 10.0.0.100 to 10.0.0.200
Now that I'm back at home, I have a little more information. Good advice on the backup configuration. I had forgotten about that capability.
I did check with all of the devices regarding DHCP. That's part of what passes for my network strategy: The router assigns all IP addresses with maybe two static exceptions that I use for development. Both exceptions were powered off for the entire time.
The devices that were not given their assigned IP addresses were 5 PoE cameras (a mix of Amcrest and TrendNET), two ancient Synology NAS DS220, and two homebuilt PCs for surveillance DVR and HTPC respectively. Other wired devices are DHCP without assignments and they came up just fine (XBOX, Blu-Ray Player, etc.)
Interestingly, the wireless devices with assignments (a couple Raspberry Pi, cell phones, and a Rock64 SBC) seem to have been assigned IPs correctly. I didn't verify that, but I never did the individual power cycle on those devices and I didn't think to check on them until after the DHCP lease had expired.
Total number of network devices is around 40-43 depending on what I have flipped on at any time.
The ISP modem is a FIOS G1100. It is not in pass-through mode. There are 2 devices connected to it (one is the RS280 router) all with static IP addresses in the 192.168.0.X range
The PoE switches are 2 CQENPR CL2080G 8 port PoE switches and a TP-Link 5G10080 Gigabit switch for non-PoE connections. Everything goes through a switch of some form. Nothing is connected directly to the router.
The RS router is recommended and suggested to be in the pass thru section of the G1100 hostrouter to help avoid NAT issues.
Sounds like possible some issues being seen with the PoE switches maybe involved during a power cycle as well. Maybe a timing issue with router, switches and these devices handling the coming to ready and not completing if a power cycle or OFF to back ON is seen on the system.
Are these static exceptions on these devices set outside of the routers default IP address range? Static IP address configurations differ from IP address reservations.
Static IP address configurations are set ON devices, not the router, and are out side of a default DHCP IP address pool range. IP address reservations are set on the host router and with in the routers default IP address pool range.
Interestingly, the wireless devices with assignments (a couple Raspberry Pi, cell phones, and a Rock64 SBC) seem to have been assigned IPs correctly.
That fits my hypothesis on the timing window. When I restart my orbi, the wired network tends to come up a bit earlier than the wireless. The basic idea is that the device is gettiing the address before the reservation table is loaded, and of course has no reason to renew it until the lease expires.
My guess is that if you are able to reproduce it, then power cycling the switch or removing/reinserting the ethernet cable should result in getting the correct address.
Whether my idea is correct or not, I think one easy test is to power down some of the devices (maybe the cameras) and the router. Then power up the devices, wait a bit, and then power up the router. Just restarting the router probably wouldn't replicate it, as the devices would have no reason to use DHCP until their lease time is up.
