New Orbi firmware 2.1.2.18 update issues?

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

---