NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AmitR
Jan 17, 2018NETGEAR Employee Retired
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...
rhester72
Jan 26, 2018Virtuoso
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.
aaz
Jan 27, 2018Virtuoso
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=64
Ping 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
- webminsterJan 27, 2018Luminary
I think none of us are sure why, either. Mine, at 2.1.2.18, in AP mode. Pinging a host on my wired network (my gateway):
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=8ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=105ms TTL=64
Reply from 192.168.1.1: bytes=32 time=336ms TTL=64
Reply from 192.168.1.1: bytes=32 time=206ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64Unlike 2.1.1, at least it isn't dropping any. But the serious wobble isn't right (how bad it wobbles varies a lot). Testing same with previous ASUS RT-AC88U doesn't show this behavior.
- aazJan 27, 2018Virtuoso
Are you sure you don't have any loops on your network with wired/wireless devices? I have heard that Sonos can do that if you plug in all of them - apparently you are only supposed to plug in one Sonos device and let the rest connect wireless using its own network. Something is on your network that is causing delays. Any android devices?
I should mention this ping time was generated while my kid is watching a 4K streaming source and with 25 connected devices.
I have the RBK53 with the two satellites - upgraded to 2.1.2.18 for the past week and it's been stable.
- webminsterJan 27, 2018Luminary
I'm happy for you.
My network is otherwise happy, no loops, no issues. And was, as mentioned, with previous APs.
- rhester72Jan 27, 2018Virtuoso
wrote: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 = 1ms1ms? Over wireless? That's...unlikely. Are you plugged into the router via Ethernet, perhaps?
- linkwrtJan 27, 2018Guide
wrote:
wrote: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 = 1ms1ms? Over wireless? That's...unlikely. Are you plugged into the router via Ethernet, perhaps?
It's ok 1ms. Depend by computer, wireless card and medium.
For example if you have windows 10 on a business computer with Intel wireless card you will have that ping.
Also depend software installed on your computer, like firewall from antivirus.
- linkwrtJan 27, 2018Guide
Look,
i connected over wireless a Dell latitude E6330 computer to orbi over wireless and this is my ping:
C:\Users\Link>ping -t 192.168.1.1
Pinging 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=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=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64Ping statistics for 192.168.1.1:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms
Control-C - aazJan 27, 2018Virtuoso
Yes, completely wireless. The computer is a Dell XPS1 about 3 years old running windows 10 pro. Connecting to the router direct all wireless, the Orbi is running as the router.
I've seen it jitter a bit more when connected via a satellite, but really on an LAN you should not be seeing constant double digit ping times, that would indicate that your network is not happy and something is causing that latency.
- linkwrtJan 27, 2018Guide
wrote:Yes, completely wireless. The computer is a Dell XPS1 about 3 years old running windows 10 pro. Connecting to the router direct all wireless, the Orbi is running as the router.
I've seen it jitter a bit more when connected via a satellite, but really on an LAN you should not be seeing constant double digit ping times, that would indicate that your network is not happy and something is causing that latency.
Lowest ping over LAN 0.3 - 0.4 ms, jitter 0.3ms-0.7ms depend on traffic.
- timchJan 27, 2018Luminary
Up 10 days now on 2.1.2.18, still rock solid. Running in AP mode behind a BT Smart Hub with mixed network of wired and wireless.
- webminsterJan 27, 2018Luminary
wrote:
I've seen it jitter a bit more when connected via a satellite, but really on an LAN you should not be seeing constant double digit ping times, that would indicate that your network is not happy and something is causing that latency.I don't see "constant" excessive ping RTTs, as shown only random swings into them. The bulk of packets return in a few ms. I'll agree, something is causing it. As mentioned, the only change is the Orbi - going back to the ASUS restores the normal ping times. Pings from any box anywhere on the wired GB network to another shows consistent sub-ms RTTs.
- aazJan 27, 2018Virtuoso
Sounds like interference with the Orbi wifi. I assume you've tried changing channels, and did a network scan to see what else is around.
- webminsterJan 27, 2018Luminary
Yes.
- OdokJan 28, 2018AspirantTurning off daisy chaining seems to have worked for me too. Pity, it’s a good feature.
- TgtermJan 28, 2018Guide
Daisy chain off for several days. Since then, no major drops. A few times, my iPad seemed to have to think a little longer than one would expect. But, prior to turning off Daisy Chaining, I would have to reset a satellite pretty frequently due to 'no internet connection' error when looking at my wifi settings on my iPad. Haven't gotten that since.
No no other devices having issues right now, so maybe it's my older iPad acting up at this point. Samsung S8 is fine, as are my PCs, Fire TV streaming, Amazon Echoes, and Nest camera.