NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New Firmware v2.5.0.38
All RBK 5 series Orbi's. FW not yet available on the download site for manual installation... Please perform a BACKUP configuration to file. Then update the RBS first then RBR lastly. Factory re...
Yes
This firmware update is really buggy. I have not re-installed any old Firmware as I am still dealing with the garbage Firmware that’s installed now. :(
BIG9MM wrote:
This firmware update is really buggy. I have not re-installed any old Firmware as I am still dealing with the garbage Firmware that’s installed now. :(
New FW feature will likely bring along new bugs that will affect one type of setup and not the other. If you go back to the future, you will find similar statements from other Orbi users for a particular firmware version that's rock solid for your setup.
From my experience, Orbi will take a while to reach steady state, especially if you have many IoT devices or LAN clients that are still hanging on to their old IP addresses until their leases expire. If Orbi reboots during this window, Orbi DHCP server could be ditching out some of those old addresses to other clients, which would result in duplicate IP addresses on the LAN network. The sad part here is that it will take a while for Orbi to populate the attached devices page, if all at, in order to check for duplicate IP addresses. It boils down to which client wins the race to get new/old IP address. A side effect of that would be connected clients, but not able to access internet, or frequent reboots, which could cause wired/WiFi hickups.
A general workaround would be to force all devices to renew their IP addresses regardless of its DHCP lease time, which could be done via network reboot, forget WiFi networks, etc.,
A solution that works for me in general, regardless of firmware versions, is to disconnect all the LAN clients from Orbi/Satellites, i.e, power off all the switches, prior to FW update. Once the FW has been updated, shutdown all Satellites, then reboot the main Orbi. Wait until it's stable (~15mins). Next power up each Satellite, one at a time. Once the Orbi network is up and running, power up all the switches, one at a time. This process will force all clients to release/renew their IP addresses. YMMV.
Just to show duplicate IP addresses in action...
See attached file and look at the first two rows, both with same IP address, 192.168.1.4, which was assigned/associated LAN/WiFi clients via Satellite-1.
SW_ wrote:See attached file and look at the first two rows, both with same IP address, 192.168.1.4, which was assigned/associated LAN/WiFi clients via Satellite-1.
Do you remember if the Attached Devices page also showed the two devices with the same IP address?
The reason I ask is my understanding has been that Access Control is by MAC address. This display might have been saying, "I saw these allowed devices on the network and these are the IP's they had at the time I saw them." (Not trying to excuse Netgear. Simply wondering how things work.)
CrimpOn wrote:
SW_ wrote:See attached file and look at the first two rows, both with same IP address, 192.168.1.4, which was assigned/associated LAN/WiFi clients via Satellite-1.
Do you remember if the Attached Devices page also showed the two devices with the same IP address?
The reason I ask is my understanding has been that Access Control is by MAC address. This display might have been saying, "I saw these allowed devices on the network and these are the IP's they had at the time I saw them." (Not trying to excuse Netgear. Simply wondering how things work.)
Yes, that's where I first noticed when my network becomes unstable. It's how I'm able to fix my network. For stubborn clients, I just remove/reboot those clients as needed. See attached file from Obri Attached Devices page, the first row and the last row.
