NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New Orbi firmware 2.1.2.18 update issues?
I noticed that there was a new firmware version 2.1.2.18 for Orbi RBK50. Has anyone installed this version, and has there been any issues after the installation. Please provide any details that you...
I just bought an Orbi100 kit. I upgraded to firmware RBR50-V2.1.2.18 and RBS50-V2.1.2.18
The Wired Satellite backhaul has an irregular response. Have other users encountered the same problem? I'm the only device connected to the 5g; WiFi scan shows no other network on that frequency.
This is a sample ping from wireless client to satellite RBS50:
MACBOOKPRO-C8A8-298:~ philippeflichy$ ping 192.168.223.121
PING 192.168.223.121 (192.168.223.121): 56 data bytes
64 bytes from 192.168.223.121: icmp_seq=0 ttl=64 time=2.133 ms
64 bytes from 192.168.223.121: icmp_seq=1 ttl=64 time=2.346 ms
64 bytes from 192.168.223.121: icmp_seq=2 ttl=64 time=2.372 ms
64 bytes from 192.168.223.121: icmp_seq=3 ttl=64 time=3.092 ms
64 bytes from 192.168.223.121: icmp_seq=4 ttl=64 time=4.352 ms
64 bytes from 192.168.223.121: icmp_seq=5 ttl=64 time=2.804 ms
64 bytes from 192.168.223.121: icmp_seq=6 ttl=64 time=108.457 ms
64 bytes from 192.168.223.121: icmp_seq=7 ttl=64 time=72.484 ms
64 bytes from 192.168.223.121: icmp_seq=8 ttl=64 time=58.553 ms
64 bytes from 192.168.223.121: icmp_seq=9 ttl=64 time=1.915 ms
64 bytes from 192.168.223.121: icmp_seq=10 ttl=64 time=1.409 ms
64 bytes from 192.168.223.121: icmp_seq=11 ttl=64 time=392.419 ms
64 bytes from 192.168.223.121: icmp_seq=12 ttl=64 time=1.775 ms
64 bytes from 192.168.223.121: icmp_seq=13 ttl=64 time=2.198 ms
64 bytes from 192.168.223.121: icmp_seq=14 ttl=64 time=1.757 ms
64 bytes from 192.168.223.121: icmp_seq=15 ttl=64 time=2.186 ms
64 bytes from 192.168.223.121: icmp_seq=16 ttl=64 time=1.440 ms
64 bytes from 192.168.223.121: icmp_seq=17 ttl=64 time=2.411 ms
64 bytes from 192.168.223.121: icmp_seq=18 ttl=64 time=2.248 ms
64 bytes from 192.168.223.121: icmp_seq=19 ttl=64 time=103.525 ms
64 bytes from 192.168.223.121: icmp_seq=20 ttl=64 time=85.235 ms
64 bytes from 192.168.223.121: icmp_seq=21 ttl=64 time=76.098 ms
64 bytes from 192.168.223.121: icmp_seq=22 ttl=64 time=63.008 ms
64 bytes from 192.168.223.121: icmp_seq=23 ttl=64 time=2.546 ms
64 bytes from 192.168.223.121: icmp_seq=24 ttl=64 time=2.155 ms
64 bytes from 192.168.223.121: icmp_seq=25 ttl=64 time=1.955 ms
64 bytes from 192.168.223.121: icmp_seq=26 ttl=64 time=2.596 ms
64 bytes from 192.168.223.121: icmp_seq=27 ttl=64 time=2.144 ms
64 bytes from 192.168.223.121: icmp_seq=28 ttl=64 time=2.824 ms
64 bytes from 192.168.223.121: icmp_seq=29 ttl=64 time=1.368 ms
64 bytes from 192.168.223.121: icmp_seq=30 ttl=64 time=2.640 ms
64 bytes from 192.168.223.121: icmp_seq=31 ttl=64 time=1.688 ms
64 bytes from 192.168.223.121: icmp_seq=32 ttl=64 time=2.983 ms
64 bytes from 192.168.223.121: icmp_seq=33 ttl=64 time=73.367 ms
64 bytes from 192.168.223.121: icmp_seq=34 ttl=64 time=36.703 ms
64 bytes from 192.168.223.121: icmp_seq=35 ttl=64 time=110.634 ms
64 bytes from 192.168.223.121: icmp_seq=36 ttl=64 time=1.947 ms
64 bytes from 192.168.223.121: icmp_seq=37 ttl=64 time=1.873 ms
64 bytes from 192.168.223.121: icmp_seq=38 ttl=64 time=2.265 ms
64 bytes from 192.168.223.121: icmp_seq=39 ttl=64 time=2.823 ms
64 bytes from 192.168.223.121: icmp_seq=40 ttl=64 time=2.033 ms
64 bytes from 192.168.223.121: icmp_seq=41 ttl=64 time=1.616 ms
64 bytes from 192.168.223.121: icmp_seq=42 ttl=64 time=2.695 ms
64 bytes from 192.168.223.121: icmp_seq=43 ttl=64 time=123.573 ms
64 bytes from 192.168.223.121: icmp_seq=44 ttl=64 time=3.054 ms
64 bytes from 192.168.223.121: icmp_seq=45 ttl=64 time=6.431 ms
64 bytes from 192.168.223.121: icmp_seq=46 ttl=64 time=2.637 ms
64 bytes from 192.168.223.121: icmp_seq=47 ttl=64 time=117.351 ms
64 bytes from 192.168.223.121: icmp_seq=48 ttl=64 time=30.336 ms
64 bytes from 192.168.223.121: icmp_seq=49 ttl=64 time=13.624 ms
64 bytes from 192.168.223.121: icmp_seq=50 ttl=64 time=1.602 ms
64 bytes from 192.168.223.121: icmp_seq=51 ttl=64 time=2.717 ms
64 bytes from 192.168.223.121: icmp_seq=52 ttl=64 time=2.014 ms
64 bytes from 192.168.223.121: icmp_seq=53 ttl=64 time=2.057 ms
64 bytes from 192.168.223.121: icmp_seq=54 ttl=64 time=3.341 ms
64 bytes from 192.168.223.121: icmp_seq=55 ttl=64 time=1.534 ms
64 bytes from 192.168.223.121: icmp_seq=56 ttl=64 time=2.675 ms
64 bytes from 192.168.223.121: icmp_seq=57 ttl=64 time=125.058 ms
64 bytes from 192.168.223.121: icmp_seq=58 ttl=64 time=108.228 ms
64 bytes from 192.168.223.121: icmp_seq=59 ttl=64 time=90.566 ms
64 bytes from 192.168.223.121: icmp_seq=60 ttl=64 time=2.118 ms
64 bytes from 192.168.223.121: icmp_seq=61 ttl=64 time=1.877 ms
64 bytes from 192.168.223.121: icmp_seq=62 ttl=64 time=1.315 ms
^C
Yes, I have the irregular ping times on local network as well. 2.1.2.18 so far has been better than 2.1.1.16 and 2.1.2.10, which actually appeared to drop pings (may have actually been just way-too-long returns).
I think others have observed similar issues on wide variances of ping response times. I've compared the tests to previous ASUS router, it definitely originates in the Orbi. Either some QoS issue or something - I have tested same when connected to the router instead of satellite, and also get the variances - just not quite as bad as when going through the satellite.
PhiloF wrote:I just bought an Orbi100 kit. I upgraded to firmware RBR50-V2.1.2.18 and RBS50-V2.1.2.18
The Wired Satellite backhaul has an irregular response. Have other users encountered the same problem? I'm the only device connected to the 5g; WiFi scan shows no other network on that frequency.
This is a sample ping from wireless client to satellite RBS50:
MACBOOKPRO-C8A8-298:~ philippeflichy$ ping 192.168.223.121
PING 192.168.223.121 (192.168.223.121): 56 data bytes
64 bytes from 192.168.223.121: icmp_seq=0 ttl=64 time=2.133 ms
64 bytes from 192.168.223.121: icmp_seq=1 ttl=64 time=2.346 ms
64 bytes from 192.168.223.121: icmp_seq=2 ttl=64 time=2.372 ms
64 bytes from 192.168.223.121: icmp_seq=3 ttl=64 time=3.092 ms
64 bytes from 192.168.223.121: icmp_seq=4 ttl=64 time=4.352 ms
64 bytes from 192.168.223.121: icmp_seq=5 ttl=64 time=2.804 ms
64 bytes from 192.168.223.121: icmp_seq=6 ttl=64 time=108.457 ms
64 bytes from 192.168.223.121: icmp_seq=7 ttl=64 time=72.484 ms
64 bytes from 192.168.223.121: icmp_seq=8 ttl=64 time=58.553 ms
64 bytes from 192.168.223.121: icmp_seq=9 ttl=64 time=1.915 ms
64 bytes from 192.168.223.121: icmp_seq=10 ttl=64 time=1.409 ms
Thanks for confirming! I have the same amount of drops when connecting to the main unit. It is so bad that I have audio drops I never encountered this with my previous Apple system... Wondering if I should send all these supposed marvels back to Amazon .... The coverage and the signal are definitely very good but what's the point if I cannot listen to my music ?)