Reply
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1

I tested this firmware using RBS50 on next room, between 1 wall, and i get also using wireless 650-700mbps.
So this is very good.
I don't see where i can reboot RBS50 satellite.
Next test was latency: between RBS50 satellite and RBS50 router i aget 0.4-0.7ms, but latency is between 0.5-0.7ms, and can get lower.
Note that MU-MIMO and beamforming is enabled.

Message 51 of 121
Highlighted
Virtuoso

Re: Announcing availability of OrbiOS 2.1


@linkwrt wrote:

I tested this firmware using RBS50 on next room, between 1 wall, and i get also using wireless 650-700mbps.
So this is very good.
I don't see where i can reboot RBS50 satellite.
Next test was latency: between RBS50 satellite and RBS50 router i aget 0.4-0.7ms, but latency is between 0.5-0.7ms, and can get lower.
Note that MU-MIMO and beamforming is enabled.


Sub-millisecond latency over wireless?  Impossible.

 

Measured since July of last year, I'm showing a bare-minimum latency of 1.3ms, an

average of 4.5ms, and spikes to over 100ms.

 

Message 52 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1

Seems orbi satellite doesn't like Europe country.

It always select 2.4GHz.

Message 53 of 121
Highlighted
Luminary

Re: Announcing availability of OrbiOS 2.1

in reply to linkwrt, I am not sure what you mean but if it helps, my Orbi and Satellite is working perfectly in UK.  After start up, the satellite connects to the router initially on 2.4 GHz then after about a minute on 5GHz; I am getting superb speeds off the satellite on both bands.  

 

My Orbi was purchased in th UK but I guess you might have problems if you bought a US version and then tried to use it in Europe due to differing hardware to cope with regulatory differences.

Message 54 of 121
Highlighted
Aspirant

Re: Announcing availability of OrbiOS 2.1

My update to rbr50 became stable after I turned off the daisy chain - don't know it go to default on with this new option when I have only one rbs. I was having reboot issues after the update until I unchecked the daisy chain box

Message 55 of 121
Highlighted
Tutor

Re: Announcing availability of OrbiOS 2.1

Weird. Have been running 2.1.2.18 for over a week and now suddenly show in attached devices that satellite-2 is wired to satellite-1 but they are definitely wireless.

Model: RBK53| Orbi Router + 2 Satellites Orbi WiFi System
Message 56 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1

I got the same, I got one sat that uses Ethernet back haul, the other is connected using WiFi to the first sat (daisy chain). However, the router shows both connected using Ethernet. But when I log on to the sat it shows WiFi back haul.
I think this is just a gui error, nothing to worry about.
Message 57 of 121
Highlighted
Aspirant

Re: Announcing availability of OrbiOS 2.1

Thanks OrbiJ. Carefully optimistic that this (deactivating daisy chaning) helped me too. Since the update I had multiple RBR reboots every day, disconnecting my devices. Since unchecking the daisy chain option it has not rebooted.

(RBR50 with two RBS50, all on 2.1.2.18)

Message 58 of 121
Highlighted
Aspirant

Re: Announcing availability of OrbiOS 2.1

Manually upgraded from Beta 2.1.2.10 which has been quite stable. CPU had dropped from 36% to 11.7%. Thruput through concrete floor to satellite to PC giving 98mb/s through 100mb/s fibre connection, 21 devices connected.

 

This release is looking good!, will check over the next few days for stability (2.1.2.10 was good already), but you guys seems to have the issue in hand at last, and are restoring my faith in my Orbi which, bar the Devember release fiasco, has been an awesome product.

 

Keep up the good work, this is ging in the right direction! Hope to switch firmware updtes back to auto in the coming weeks....

Message 59 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1


wrote:

Thanks OrbiJ. Carefully optimistic that this (deactivating daisy chaning) helped me too. Since the update I had multiple RBR reboots every day, disconnecting my devices. Since unchecking the daisy chain option it has not rebooted.

(RBR50 with two RBS50, all on 2.1.2.18)


i have daisy .. enabled.

No issue.

Message 60 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1

Similar experience here with Daisy Chain on 2.1.2.18.  When I have it enabled, frequent 'no internet connection' issues with satellites when using an iPad.  Since I disabled it, so far so good...

Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Message 61 of 121
Highlighted

Re: Announcing availability of OrbiOS 2.1

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...

Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Message 62 of 121
Highlighted
Apprentice

Re: Announcing availability of OrbiOS 2.1

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?

Message 63 of 121
Highlighted
Star

Re: Announcing availability of OrbiOS 2.1

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.

 

Message 64 of 121
Highlighted
Luminary

Re: Announcing availability of OrbiOS 2.1


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.


 

Model: RBK50| Orbi AC3000 High-Performance Tri-Band WiFi System
Message 65 of 121
Highlighted
Virtuoso

Re: Announcing availability of OrbiOS 2.1


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.

Message 66 of 121
Highlighted
Virtuoso
Virtuoso

Re: Announcing availability of OrbiOS 2.1

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

Message 67 of 121
Highlighted
Luminary

Re: Announcing availability of OrbiOS 2.1

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=64

 

Unlike 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.

 

 

Message 68 of 121
Highlighted
Virtuoso
Virtuoso

Re: Announcing availability of OrbiOS 2.1

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.

Message 69 of 121
Highlighted
Luminary

Re: Announcing availability of OrbiOS 2.1

I'm happy for you.

My network is otherwise happy, no loops, no issues.  And was, as mentioned, with previous APs.

 

Message 70 of 121
Highlighted
Virtuoso

Re: Announcing availability of OrbiOS 2.1


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=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


1ms?  Over wireless?  That's...unlikely.  Are you plugged into the router via Ethernet, perhaps?

Message 71 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1


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=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


1ms?  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.

 

Message 72 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1

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=64

Ping 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

Message 73 of 121
Highlighted
Virtuoso
Virtuoso

Re: Announcing availability of OrbiOS 2.1

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. 

Message 74 of 121
Highlighted
Guide

Re: Announcing availability of OrbiOS 2.1


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.

Message 75 of 121
Top Contributors
Announcements