NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FURRYe38
Oct 17, 2022Guru
New - MR60 / MS60 Firmware Version 1.1.7.132 Released
New Features and Enhancements: 10/17/2022
Fixed Armor might be deactivated issue after FW update.
Fixed SPC doesn’t work after users block devices in Access Control.
Support Xunyou service in...
MTester
Nov 29, 2022Aspirant
I have 1 MR60 router and 3 MS60 satellites. All were running the current 1.1.7.132.
I am not certain when mine updated their firmware, but I've been noticing issues over the past few weeks. Mostly that wifi seemed to be bouncing up and down randomly (with an IP Configuration failed error which would eventually go away), while ethernet was stable. But today that all came to an end. Both wifi and ethernet stopped working, though I could confirm the ISP was fine.
Through hours of trial and error, where some wifi devices would work, and some ethernet devices would work, and the rest just wouldn't, I came to the conclusion it was an issue with DHCP.
Statically assign an address, wifi or ethernet, and it was fine. DHCP, a couple would work, most not. I think it is having trouble either reassigning addresses, or freeing up old ones.
I've had the same setup a year now, and no problems. I'm showing 139 devices attached though, and that's not right. I might have about 70-80 actual devices counting lights, watches, phones, computers, TVs, etc.
My gut fix was to factory reset and start over. Before doing that though, I turned off auto-updates on firmware and reverted back to 1.1.6.124. After doing that, and rebooting the router/satellites, it was a little sluggish, but after about 15 minutes, everything started connecting fine and no problems since. No factory reset needed.
Netgear, look at the DHCP stuff and test on a bigger scale than what you apparently are doing. Either the cache is not getting flushed properly between disconnects/reconnects, or something. Also, you need to add a better check in there for assigning an IP to a device when another device already has that IP, AND the IP is in the DHCP range. I understand if a device has a static IP and that can cause a conflict. But I am speaking about 2 devices, both on DHCP, and both end up with the same IP. That should be something you can avoid.