NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAXE500 DHCP Address reservation issues
Hi, All. I'm an IT Professional of 20+ years. I've never had this issue with any router I've ever used, and I'm totally stumped on how to fix it.
I just bought this router a few weeks ago, and all was well. All of a sudden, devices I reserved in LAN setup are showing up with different IP Addresses from the ones I reserved. The reserved addresses still show in the reservation list, but under Attached Devices, the address is something totally different. Perfect example: I have my Synology DiskStation reserved to 192.168.0.5. My router changes the address to 192.168.0.246 unless I set it up as Static on the DiskStation.
I'm currently running firmware V1.0.9.78_2.0.38, which I believe is the current. My last router was a NightHawk X10 R9000, and all was rock solid without ANY issues at all.
I have saved the configuration, factory defaulted and re-loaded the configuration with no luck. I've even factory defaulted and manually re-added the addresses with no lock. Every time I factory reset, I get random devices working with their assigned addresses, but other random devices get assigned in the 240 range. My reserved table is 192.168.0.3 - 192.168.0.25, with 26 starting up DHCP.
I'm really feeling that his router isn't ready for prime time. If anyone has any suggestions, I'd love to hear them.
4 Replies
How many reserved IP addresses do you have? Is it just that 25? I know there was an issue with more than 64 that is supposed* to be fixed in the next firmware release.
I've got a raxe500 but i've only got a couple (4?) reserved ip addresses for things like server/printer. I haven't had any issues with them getting switched. are you able to track if it happens with just 1 or 2 or at what point it starts dropping?
what happens if you leave it on the default ip address configuration of 192.168.1.1? (not sure why it should matter for switching to the 192.168.0.1 but worth a shot)
I have 18 reservations in total. As you can tell, I have an elaborate home network. The weird thing is that the reservation dropping is random. It drops my reservations for the 8th, 9th and then the 12th through 17th reservations. All the other ones are fine. It's really bizarre. Even then, it assigns addresses in the 2xx range (not the 26 where DHCP is supposed to start).
I've tried switching over to 192.168.1.X, and I've had issues there as well. During the reboot process, a bunch of devices (mainly WiFi light bulbs) will still have the 192.168.0.X address and are showed in Attached Devices. I really wish these routers had the ability to end the DHCP lease manually (Hint, Hint NetGear!).
I've also tried changing the pool from using 192.168.0.26 through 254 to 100 (hoping that it would shake everything up). It didn't. Devices (wired and wireless) still showed up in the .200 range even after that.
My fix so far is manually changing the address to static (shame on you, NetGear). I'm going to change them back to DHCP after 24 hours have elapsed hoping that the router will reassign them to what they should be after their leases are up. Unfortunately I can't do this with all the devices (I have 3 SiliconDust HDHomeRuns (2 (4 tuners) and 1 (2 tuner)). and it's just killing me that the 4 tuner versions are .12 and .13, with the Duo being .234.
I'm disgusted that Netgear let this router out with so many issues. I've had a issue with my Synology DS918+ and Link Aggregation on this router as well. (I just gave up and set up LACP on my GS324T (and it took two seconds)). It worked PERFECTLY on my R9000 (my previous router). Like I said, I've always used Netgear, and they just disappoint more and more. I'm buying a Protectli Vault to do end-to-end encryption, and if this is still the issue, I'm going to use this router for WiFi6, and have the Protectli dish out addresses.
Any other ideas, or any new things to try? You were saying that a newer firmware is coming out soon. Maybe this will address this?
Not sure if it fixes that issue or not because I didn't have the issue prior. Maybe is about all I can say?
