NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
2.5.1.16 Results Only
Could we please have a post that ONLY contains reports of firmware 2.5.1.16?
i.e. "My Orbi is now at firmware 2.5.1.16 and I observe:
- No change. Everything is the same as before. What worked continues to work. What failed continues to fail.
- THIS has been fixed. Did not work before, and now it does
- THIS is now "broken". It worked before, and now it doesn't
No arguments about what people should have done or why. Just observations.
35 Replies
Same as before. RBK50 working well after FW update to v16. No factory reset since coming back from Voxels FW.
Been running 2.5.1.16 for a week without any problems. Device discovery does seem to be improved and, so far, the WebUI info matches the app info. No other items noticed. My changes to DEV_show_device.htm to add column sorting work in 2.5.1.16 without change.
Scott
Anyone who uses Circle notice any improvements? Last firmware borked it up royally.
- Since flashing 2.5.1.16 I haven't noticed any of the issues I've had in the past giving problems...
1) Disney Circle seems to be working fine. Adjustments can be made in Circle app and Orbi reacts as it should without having fits.
2) Fewer false alarms and false positives from Armor. It got so bad that I tried sending a bug report to Bitdefender and the Orbi wouldn't even capture its logs. All seems well now.
3) DHCP reservations were causing device disconnects. All seems to work as it should.
4) Device naming and icon assignments seem to be sticking between app and Orbi GUI... but I wish that there were the same selection of icons in the app as in the web GUI.I can confirm that Circle appears to be working again without killing my Internet connection.
I have been running v2.5.1.16 for a month (I received an early beta release of it for an open ticket). For me, I never had the incomplete device list issue others saw with 2.5.1.8, so I see no improvements with 2.5.1.16 on my setup. I still have 4 open issues that have tickets with NG support at L2 or Engineering levels:
1) Orbi Android App cannot change device icons
2) Orbi Android App icon is incorrect for "smart locks", shows "network" device instead
3) DHCP logging is inconsistent (logs them until rebooted, then does not log them until rebooted again)
4) dnsmasq process for DNS server does not resolve local LAN hostnames
Of these, #4 above is the most critical bug, that they do not appear to want to fix as I have had it open for 12 months!
I do not use Circle or Bitdefender.
Fixed (so far): 2.5.1.16 seems to be better at maintaining continuous wi-fi signal. On 2.5.1.8, the RBS50 satellite would appear reboot itself several times a week (as evidenced by loss of coverage for several minutes and the appearance of the blue ring). Fingers crossed on results as the week progresses.
Side note: when I first upgraded to 2.5.1.16 and did a factory reset, the RBR50 router couldn't connect to the WAN (a big red "NO INTERNET"). After a couple of reboots, it was able to connect. Not sure if this was a one-time problem, but it does make me reluctant the next time I have to reboot the router.
Correction: same as before (2.5.1.16 vs. 2.5.1.8) - the RBS50 satellite still periodically reboots itself (blue ring appears for several minutes while wi-fi is down).
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?Has a factory reset and setup from scratch been performed since last FW update?
Do you have just 1 RBS or do you have more?
changds wrote:Correction: same as before (2.5.1.16 vs. 2.5.1.8) - the RBS50 satellite still periodically reboots itself (blue ring appears for several minutes while wi-fi is down).
Unfortunately, the satellite ethernet ports work for the backhaul but not a client.
Device scanning speed is much faster and naming is working.
- "Unfortunately, the satellite ethernet ports work for the backhaul but not a client."
Not sure what this statement means. The RBS50s are basically a wireless switch, unmanaged switch. Wirelessly connecting to clients and backhauling to the RBR50 wirelessly or via ethernet.My RBS20 has two ethernet ports, one being used for the backhaul and the second I hoped to wire to an Ethernet device.
A few older posts indicate that this is a firmware issue, not a configuration or hardware issue.
Looks like the SOAP information if slightly broken in 16. I first noticed it last night when I download the latest iOS app. I thought the app was the problem but I can access the SOAP information directly now and the problem is the SOAP information the app is getting. The app is reporting the number of satellites incorrectly and all the associated satellite info. Last night the app said I had 2 satellites - i have 3. Today the app thinks I have one satellite. Interestly, the connected devices are correct and I have confirmed devices are connected to the satellites and working. The WebUI reports the satellites correctly.
In addition to correcting the bug in 16, it might be time to get the design right and have only one definitive source of information. The idea that the WebUI reports different information from the SOAP interface is a design error rather than a bug. One source for definitive data.
Since updating to v2.5.1.16, I am having brief moments of network disruption experienced by all devices on the network. My husband and I will be on our laptops while music is streaming on our tv and all devices will experience a brief period of no connectivity. All devices show full strength connectivity before the interruption. Sometimes the devices still show connection to the network even though no data seems to be flowing. In these times, I try to connect to Orbi's admin page, but cannnot reach it. When I am able to get data again and view the Orbi logs, I will see the reconnection of devices immediately after the momentary connection blip, which suggests the devices did indeed lose connection. I have not had any connection issues in the 3 years of owning the Orbi and there have been no new devices added to the network in the last few months. Something is broken, but I don't know what.
We experienced the same thing. Our RBS50 satellite seemed to be the culprit and bring down the whole network for 5+ minutes while it rebooted. After multiple attempts at firmware changes, gave up. Bought the SRK60 Orbi Pro (which runs on different firmware) and has been stable for 8+ days so far.
Has a factory reset and setup from scratch been performed since last FW update?
Press the back reset button for 15 seconds then release.What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected. https://kb.netgear.com/000036466/How-far-should-I-place-my-Orbi-satellite-from-my-Orbi-router
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Try enabling Beamforming and MIMO(MIMO may or maynot be needed) and WMM. Under Advanced Tab/Advanced Settings/Wireless Settings
Try disabling the following and see:
Armor, Circle, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Set Short preamble instead of Long preamble modes. Save settings and reboot the router and satellite(s).
changds wrote:We experienced the same thing. Our RBS50 satellite seemed to be the culprit and bring down the whole network for 5+ minutes while it rebooted. After multiple attempts at firmware changes, gave up. Bought the SRK60 Orbi Pro (which runs on different firmware) and has been stable for 8+ days so far.
