Jump to content
Reminder, starting today you will no longer be able to login to the forum using your display name, to login you must now use your email address. ×

XR700 Drops DHCP lease/IP's on anything above .20 FW


Recommended Posts

Hi All,

Some background. 

I have a Arris surfboard in front of a XR700 then a Netgear prosafe gig switch that runs out to our "smart house", about 20 hue bulbs and 10 or so smart switches and three webcams(one Nest, two Wyze). I am skipping the hardline internet but there is a decent amount of  game consoles/Tv's/utility devices on that.

 

Currently we are running on the .20 firmware but a few months ago I updated to whatever was current then and most of our wireless devices lost connection a few hours later, I was not home but everything just went "offline". I checked the logs and I saw a bunch of lease renewals which I thought was odd.  So I wiped the unit and went back to .20. 

Today I tried to upgrade again because I personally feel better being able to run whatever the current public release is.

The exact moment the router came back up my MacBook Air(current gen) was in an endless loop of no wifi/wifi. MacOS was saying I had a invalid IP or self assigned IP, a renewal did no good. When I connected via a hardline and turned off WiFi I got that attached error, which looks like the same issue I saw last time. So I then tried to reload my config which did me no good. So I went back to .20 and then reloaded and I am semi back up and running. Some of my smart switches won't reconnect nor will any of the Wzye cams but I have not fully wiped them yet since that is a fairly large PITA. 

 

When I get home I was going to reset the unit with the button on the back and reload my settings.   Anyone have any idea how I can get this to work like its supposed to? Kinda sucks that I can't run the new firmware. 

 

 

Tbl.png

2222.png

Link to comment
Share on other sites

  • Administrators

Hey, welcome to the forum!

This could be an issue with DHCP, to test try assigning a few reserved/static IPs on the router for some of the devices and see if they get disconnected when the issue happens again. Also I would suggest looking here to join the XR700 beta https://community.netgear.com/t5/Nighthawk-Pro-Gaming-Routers/XR700-Beta-Firmware/m-p/1760800#M11125 a beta firmware may resolve the issue also. If it doesn't then you can give them direct feedback on the issue.

Link to comment
Share on other sites

Thanks Fraser! Honestly I Googled around for a solution back when the first problem happened and read this same suggestion and thought "Ohh eff that". I understand how assigning statics could fix this. However I have zero interest in maintaining a DCHP pool in my own home.  A $400+ router should be able to automatically take care of this. I had a R800 before this with no issues.

Im sorry if the tone come across wrong, I just don't get it. I feel like a fool for buying this, and I totally understand this is not your problem but I don't think calling a support line is any better. I guess I can just use the unit as a coaster.

Link to comment
Share on other sites

  • Administrators

No worries totally understand. I would just suggest doing it for a few devices and then if that works we can see there is an issue with DHCP and we can forward that to the appropriate team. Try the beta instead then and see if that helps at all.

Link to comment
Share on other sites

Yes,  I think there is 2-4 others who have the same issue. all bowers are not working for I and  others. I know I personally have reset the router from interface and reset button about 6 times. I know I have also used firefox edge chrome Op something and none of them work for R apps for me.

The really weird part is R apps will work if you restart the router but about 2 hours later they fail again.

Link to comment
Share on other sites

  • 8 months later...

I just started experiencing this issue today running on v1.0.1.20. Can second the sentiment of feeling like a fool for spending so much on a router that has DHCP leasing issues. Hopefully, rolling back to v1.0.1.10 fixes it.

Is there any fix for this pending? 
 

Link to comment
Share on other sites

  • Administrators
8 minutes ago, khoix said:

I just started experiencing this issue today running on v1.0.1.20. Can second the sentiment of feeling like a fool for spending so much on a router that has DHCP leasing issues. Hopefully, rolling back to v1.0.1.10 fixes it.

Is there any fix for this pending? 
 

Hey, welcome to the forum!

Would definitely suggest signing up to the 3.0 beta as it'll most likely be fixed in that version but if not it provides the perfect opportunity for you to give us that feedback.

Link to comment
Share on other sites

29 minutes ago, Netduma Fraser said:

Hey, welcome to the forum!

Would definitely suggest signing up to the 3.0 beta as it'll most likely be fixed in that version but if not it provides the perfect opportunity for you to give us that feedback.

Worth a shot. Downgrading didn't help.

Link to comment
Share on other sites

I should add, I tried using reserved addresses and the issue persists.

Only when I set static addresses on the devices themselves do the excessive DHCP leases stop.

Here's a 20-second snippet of my log where multiple devices are re-assigned multiple times within the same second:

Quote

June 10, 2020 20:48:50: [DHCP IP: 192.168.1.30][Device Name: ESP_975F03] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:50: [DumaOS] DHCP lease change.
June 10, 2020 20:48:50: [DumaOS] DHCP new event.
June 10, 2020 20:48:49: [DumaOS] Marking device that is marked 192.168.1.30 22 35.
June 10, 2020 20:48:49: [DHCP IP: 192.168.1.32][Device Name: ESP_450889] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:49: [DumaOS] DHCP lease change.
June 10, 2020 20:48:49: [DumaOS] DHCP new event.
June 10, 2020 20:48:47: [DumaOS] Marking device that is marked 192.168.1.28 19 34.
June 10, 2020 20:48:47: [DHCP IP: 192.168.1.33][Device Name: ESP_403663] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:47: [DumaOS] DHCP lease change.
June 10, 2020 20:48:47: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.32][Device Name: ESP_450889] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.14][Device Name: ESP_037055] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.33][Device Name: ESP_403663] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.28][Device Name: ESP_E74E26] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.30][Device Name: ESP_975F03] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:46: [DHCP IP: 192.168.1.14][Device Name: ESP_037055] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:46: [DumaOS] DHCP lease change.
June 10, 2020 20:48:46: [DumaOS] DHCP new event.
June 10, 2020 20:48:45: [DumaOS] Marking device that is marked 192.168.1.30 22 35.
June 10, 2020 20:48:44: [DHCP IP: 192.168.1.28][Device Name: ESP_E74E26] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:44: [DumaOS] DHCP lease change.
June 10, 2020 20:48:44: [DumaOS] DHCP new event.
June 10, 2020 20:48:44: [DHCP IP: 192.168.1.30][Device Name: ESP_975F03] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:44: [DumaOS] DHCP lease change.
June 10, 2020 20:48:44: [DumaOS] DHCP new event.
June 10, 2020 20:48:43: [DumaOS] Marking device that is marked 192.168.1.31 24 38.
June 10, 2020 20:48:40: [DHCP IP: 192.168.1.42][Device Name: ESP_E54325] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:40: [DumaOS] DHCP lease change.
June 10, 2020 20:48:40: [DumaOS] DHCP new event.
June 10, 2020 20:48:40: [admin login] from source 192.168.1.2
June 10, 2020 20:48:30: [DHCP IP: 192.168.1.42][Device Name: ESP_E54325] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:30: [DumaOS] DHCP lease change.
June 10, 2020 20:48:30: [DumaOS] DHCP new event.
June 10, 2020 20:48:29: [DHCP IP: 192.168.1.42][Device Name: ESP_E54325] to MAC address nn:nn:nn:nn:nn:nn
June 10, 2020 20:48:29: [DumaOS] DHCP lease change.
June 10, 2020 20:48:29: [DumaOS] DHCP new event.

If there is a fix in 3.0b, this should definitely be backported. 

Right now, I have a $400 paperweight--no way I can keep this in my network.

Link to comment
Share on other sites

1 hour ago, Netduma Fraser said:

That makes sense, sometimes if that doesn't work then disabling the DHCP server completely can solve it. Let us know if you still experience it in beta.

I signed up for the beta, but didn't get an auto-reply or anything.

Is there anything special I have to do to get in on it?

Link to comment
Share on other sites

  • Administrators
13 minutes ago, khoix said:

I signed up for the beta, but didn't get an auto-reply or anything.

Is there anything special I have to do to get in on it?

That's normal, no nothing you need to do. Testers will be selected in waves and when chosen will be emailed.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...