NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Announcing availability of OrbiOS 2.1
I posted this on a different thread, but copy & pasting it here for more visibility. Let me give you a quick update on where NETGEAR is with the OrbiOS. Just before Christmas break, we paus...
Well I've been bumped to L3 support and given a special debug version of the current firmware to install and grab more logs. Hopefully this will help track down the random reboots some of us have...
How long for a Chromecast/Android fix Netgear?.. Netgear still needs to come up with a fix for their end... TP-Link, Linksys, and others have done it already... and I have all my CAST devices unplugged, and uninstalled Google Home app from my phone and I am still having issues with the Orbi, so Netgear has another issue to address also... does Netgear even care?
Fully agree that Netgear needs to address some stability and connectivity issues outside of the Chromecasr/Android bug.
- Wired backhaul is not stable and just connecting statalite to wired connection causes the Router to reboot (should be easy enough for netgear to reproduce)
- Devices randomaly disconnect and reconnect to wifi (all while stationany and with good wifi signal)
- Ping times to the router can go flactuate anywhere from 5-9ms to 20-50ms to 500+ms
P.S. Lot more stable then previous 2.1x release and beta, but not quite upto stability of even a $100 router.
wrote:Fully agree that Netgear needs to address some stability and connectivity issues outside of the Chromecasr/Android bug.
- Ping times to the router can go flactuate anywhere from 5-9ms to 20-50ms to 500+ms
+1 this.
wrote:- Ping times to the router can go flactuate anywhere from 5-9ms to 20-50ms to 500+ms
Unfortunately I have to concur with this one - I've been monitoring this quite closely since July 2017 (my graphs go that far back, 24/7), and while the average latency remains quite good (at around 4.5ms), the jitter is FAR higher with 2.1 firmware than it was on 2.0 or prior.
Not sure why you guys are seeing such high ping times to the router here is what I have
Pinging orbilogin.com [192.168.1.1] with 32 bytes of data
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64Ping statistics for 192.168.1.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms