NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi losing packets
Hello, I'm seeing packet losses with my Orbi. I have the RBK53 (RBK50, boxed with two remote Orbi devices). The Orbi is hardwired to my firewall. Also hardwired to my firewall is a Linux...
Thanks DarrenM, I appreciate the info on the update firmware.
I did see that others were still seeing packet drops with certain devices. I'm seeing packets dropped with a desktop using a Belkin USB Wifi and a laptop using a built-in Wifi.
But the new firmware is definitely worth a try - I am currently on V2.0.0.74. If it works I'll report back.
After a bit of struggle, I was able to update my RBR50 and two RBS50 units to the latest firmware V2.1.1.16.
(Serious Netgear, if my RBR50/RBS50 units appears to be working well, why do I need to reboot the RBR50 in order for the updates to work properly? And why do I need to manually update all the units? This isn't junior league.)
Anyway, the packet drops are still happening with the latest firmware V2.1.1.16. Things look OK, then packet time will increase, then there is a loss of packets. And as before, when I run the test at the same time from a hardwired system, I am not losing packets.
The below ping tests were run at the same time:
Test from Orbi system | Reply from 8.8.8.8: bytes=32 time=34ms TTL=252 Reply from 8.8.8.8: bytes=32 time=31ms TTL=252 Reply from 8.8.8.8: bytes=32 time=31ms TTL=252 Reply from 8.8.8.8: bytes=32 time=160ms TTL=252 Reply from 8.8.8.8: bytes=32 time=36ms TTL=252 Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=30ms TTL=252 Reply from 8.8.8.8: bytes=32 time=31ms TTL=252 Reply from 8.8.8.8: bytes=32 time=31ms TTL=252 Reply from 8.8.8.8: bytes=32 time=32ms TTL=252 |
Test from hardwired system | 64 bytes from 8.8.8.8: icmp_seq=23 ttl=253 time=28.9 ms 64 bytes from 8.8.8.8: icmp_seq=24 ttl=253 time=28.8 ms 64 bytes from 8.8.8.8: icmp_seq=25 ttl=253 time=29.3 ms 64 bytes from 8.8.8.8: icmp_seq=26 ttl=253 time=30.2 ms 64 bytes from 8.8.8.8: icmp_seq=27 ttl=253 time=30.3 ms 64 bytes from 8.8.8.8: icmp_seq=28 ttl=253 time=28.7 ms 64 bytes from 8.8.8.8: icmp_seq=29 ttl=253 time=29.6 ms 64 bytes from 8.8.8.8: icmp_seq=30 ttl=253 time=33.6 ms 64 bytes from 8.8.8.8: icmp_seq=31 ttl=253 time=30.7 ms 64 bytes from 8.8.8.8: icmp_seq=32 ttl=253 time=28.7 ms 64 bytes from 8.8.8.8: icmp_seq=33 ttl=253 time=29.3 ms |
So something is definitely wrong with the Orbi system where it is losing packets.
Does anyone have any thoughts on how to fix this? Thanks in advance.
Not much help, but I see similar issues on my RBK50, running 2.1.1.16, pinging hosts from my laptops to my wired network. Packet latencies and some drops. Orbi as an AP plugged into a switch. Hosts on the switch pinging other hosts on switch are fast and no loss. No idea yet why.
But, for me, the most curious thing? My gateway device for my network is at 192.168.1.1. That's where my worst loss is - pinging that address through the wireless laptop through the Orbi. Pinging other devices (different addresses), not too bad. And pinging 192.168.1.1 from other machines on the wired network is zero loss / sub-ms RTT.
Not sure why the Orbi in AP mode on its own DHCP-assigned address should have such a packet loss to the gateway. There's no duplicate addresses, no static routes, whatever.
EDIT: A little more experimentation seems to be implicating the satellite as adding latency (at least) to the issue. Getting the laptop to connect to the router seems to decrease the latency variance and decreasing the lost packets.
webminster wrote:
EDIT: A little more experimentation seems to be implicating the satellite as adding latency (at least) to the issue. Getting the laptop to connect to the router seems to decrease the latency variance and decreasing the lost packets.
Wireless add latency compared to wired. Pinging through the satellite uses two wireless hops, thus more latency than devices connected to the Orbi router. Packet loss over the WiFi would indicate RF interference and/or a marginal WiFi connection, either between your device and your AP or between the Orbi router and satellite, or both.
A little bit more information on my post - I am running my tests while connected via WiFi to the router, not a satellite.
At Webminster's suggestion, I am going to ping test different devices connected to router/satellites to see what happens.
So far I'm not losing packets. I'm not sure if it was due to the firmware update or the rebooting of the devices.
I ran a ping test to 8.8.8.8 for 1.5 days. On average, I am losing about 8 ms in latency using WiFi vs. hardwired, but I can live with that.
I'll continue to monitor to see if I get any packet losses, but so far things are looking good.
Just installed the 2.1.2.10 beta this morning, been running a couple of casual tests. Hasn't helped my latency variations though the satellite to some hardwired addresses on my local network. Variations on a local Linux box from 2ms to 300ms, sometimes no packet loss, sometimes between 1% and 20+%. The loss and variances are cyclic. Tried looking at Wifi Analyzer for any obvious conflicts on the 5G band, don't see any.