NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
High LAN latency with ORBI Mesh network
Problem: The internet speed of both my computers are quite fast (200Mbps, 5 ms latency), but the LAN speed between them are slow (10Mbps, 100ms latency)
My network setup:
* RBR20: One router & one satellite with wireless backhaul
* Two desktop computers connected to the mesh network with 5G wifi. Both are connected to the router, not the satellite.
I do most of my work by SSHing from my Windows computer to my Linux server, so the latency really kills ms. What's weird is that the ping from Windows to Linux is 100ms, but the other way is 8ms. The ping from Windows to Linux also look weird: it grows gradually from 4ms to 200ms, then falls back sharply to 4ms and start again. Look at the attached screenshot.
I can rule out the cause from my computers, because (1) I switched from another wireless router (not mesh) from another brand. They worked well on my that router. (2) I tried to ping other laptops, smart phones, and all are as high.
10 Replies
Who is your ISP and what equipment did they provide?
What is the current firmware on your Orbi device?
What device is your Orbi router connected to?
Did you reboot your ISP modem/router, before starting the Orbi router install?
Have you changed the network cable connected from the ISP device to your Orbi router?
Disable Circle, Armor, Daisy Chaining, Fast Roaming, IPv6 and uncheck 20/40Mhz Coexistence.
Enable WMM, Implicit BeamForming, Mu-MIMO
Set Short preamble mode. Save settings, reboot Orbi.1. My ISP is MyRepublic from Singapore. The fibre modem is Alctel Lucent I-240G-D. However, I don't think LAN performance is related to my ISP.
2. Please check my attached screenshot.
3. As I said, I have two computers connected to the Orbi router var 5G wifi. One is Intel NUC NUC8i3BEH running Fedora Linux. The other is a desktop PC running Windows 10.
4. I switched to Orbi router for more than a month, during which the modem and the router has rebooted a few times. Again, I don't think LAN performance has anything to do with the modem.
5. Here is my wifi setting:
2.4GHz, Enable 20/40 MHz Coexistence: Yes
2.4GHz, Enable WMM (Wi-Fi multimedia) settings: Yes
5GHz, Enable WMM (Wi-Fi multimedia) settings: Yes
Enable Daisy-Chain Topology: No
Enable Implicit BEAMFORMING: No
Enable MU-MIMO: Yes
Enable Fast Roaming: No
I have changed the router setting as you suggested (see screenshot), but the problem remains.
I visualized the pin to show the weirdness. See the attached image.
C:\Users\Wu Yongzheng>ping -n 100 192.168.1.10
Pinging 192.168.1.10 with 32 bytes of data
Reply from 192.168.1.10: bytes=32 time=6ms TTL=64
Reply from 192.168.1.10: bytes=32 time=146ms TTL=64
Reply from 192.168.1.10: bytes=32 time=163ms TTL=64
Reply from 192.168.1.10: bytes=32 time=8ms TTL=64
Reply from 192.168.1.10: bytes=32 time=185ms TTL=64
Reply from 192.168.1.10: bytes=32 time=195ms TTL=64
Reply from 192.168.1.10: bytes=32 time=205ms TTL=64
Reply from 192.168.1.10: bytes=32 time=210ms TTL=64
Reply from 192.168.1.10: bytes=32 time=215ms TTL=64
Reply from 192.168.1.10: bytes=32 time=22ms TTL=64
Reply from 192.168.1.10: bytes=32 time=14ms TTL=64
Reply from 192.168.1.10: bytes=32 time=38ms TTL=64
Reply from 192.168.1.10: bytes=32 time=48ms TTL=64
Reply from 192.168.1.10: bytes=32 time=55ms TTL=64
Reply from 192.168.1.10: bytes=32 time=64ms TTL=64
Reply from 192.168.1.10: bytes=32 time=73ms TTL=64
Reply from 192.168.1.10: bytes=32 time=81ms TTL=64
Reply from 192.168.1.10: bytes=32 time=82ms TTL=64
Reply from 192.168.1.10: bytes=32 time=94ms TTL=64
Reply from 192.168.1.10: bytes=32 time=102ms TTL=64
Reply from 192.168.1.10: bytes=32 time=109ms TTL=64
Reply from 192.168.1.10: bytes=32 time=114ms TTL=64
Reply from 192.168.1.10: bytes=32 time=134ms TTL=64
Reply from 192.168.1.10: bytes=32 time=155ms TTL=64
Reply from 192.168.1.10: bytes=32 time=158ms TTL=64
Reply from 192.168.1.10: bytes=32 time=165ms TTL=64
Reply from 192.168.1.10: bytes=32 time=172ms TTL=64
Reply from 192.168.1.10: bytes=32 time=190ms TTL=64
Reply from 192.168.1.10: bytes=32 time=202ms TTL=64
Reply from 192.168.1.10: bytes=32 time=220ms TTL=64
Reply from 192.168.1.10: bytes=32 time=28ms TTL=64
Reply from 192.168.1.10: bytes=32 time=40ms TTL=64
Reply from 192.168.1.10: bytes=32 time=49ms TTL=64
Reply from 192.168.1.10: bytes=32 time=54ms TTL=64
Reply from 192.168.1.10: bytes=32 time=63ms TTL=64
Reply from 192.168.1.10: bytes=32 time=72ms TTL=64
Reply from 192.168.1.10: bytes=32 time=87ms TTL=64
Reply from 192.168.1.10: bytes=32 time=101ms TTL=64
Reply from 192.168.1.10: bytes=32 time=115ms TTL=64
Reply from 192.168.1.10: bytes=32 time=123ms TTL=64
Reply from 192.168.1.10: bytes=32 time=11ms TTL=64
Reply from 192.168.1.10: bytes=32 time=140ms TTL=64
Reply from 192.168.1.10: bytes=32 time=141ms TTL=64
Reply from 192.168.1.10: bytes=32 time=152ms TTL=64
Reply from 192.168.1.10: bytes=32 time=160ms TTL=64
Reply from 192.168.1.10: bytes=32 time=167ms TTL=64
Reply from 192.168.1.10: bytes=32 time=182ms TTL=64
Reply from 192.168.1.10: bytes=32 time=191ms TTL=64
Reply from 192.168.1.10: bytes=32 time=11ms TTL=64
Reply from 192.168.1.10: bytes=32 time=220ms TTL=64
Reply from 192.168.1.10: bytes=32 time=40ms TTL=64
Reply from 192.168.1.10: bytes=32 time=30ms TTL=64
Reply from 192.168.1.10: bytes=32 time=57ms TTL=64
Reply from 192.168.1.10: bytes=32 time=62ms TTL=64
Reply from 192.168.1.10: bytes=32 time=64ms TTL=64
Reply from 192.168.1.10: bytes=32 time=68ms TTL=64
Reply from 192.168.1.10: bytes=32 time=85ms TTL=64
Reply from 192.168.1.10: bytes=32 time=93ms TTL=64
Reply from 192.168.1.10: bytes=32 time=101ms TTL=64
Reply from 192.168.1.10: bytes=32 time=110ms TTL=64
Reply from 192.168.1.10: bytes=32 time=119ms TTL=64
Reply from 192.168.1.10: bytes=32 time=130ms TTL=64
Reply from 192.168.1.10: bytes=32 time=136ms TTL=64
Reply from 192.168.1.10: bytes=32 time=151ms TTL=64
Reply from 192.168.1.10: bytes=32 time=8ms TTL=64
Reply from 192.168.1.10: bytes=32 time=8ms TTL=64
Reply from 192.168.1.10: bytes=32 time=816ms TTL=64
Reply from 192.168.1.10: bytes=32 time=14ms TTL=64
Reply from 192.168.1.10: bytes=32 time=21ms TTL=64
Reply from 192.168.1.10: bytes=32 time=47ms TTL=64
Reply from 192.168.1.10: bytes=32 time=47ms TTL=64
Reply from 192.168.1.10: bytes=32 time=52ms TTL=64
Reply from 192.168.1.10: bytes=32 time=68ms TTL=64
Reply from 192.168.1.10: bytes=32 time=77ms TTL=64
Reply from 192.168.1.10: bytes=32 time=80ms TTL=64
Reply from 192.168.1.10: bytes=32 time=92ms TTL=64
Reply from 192.168.1.10: bytes=32 time=97ms TTL=64
Reply from 192.168.1.10: bytes=32 time=112ms TTL=64
Reply from 192.168.1.10: bytes=32 time=124ms TTL=64
Reply from 192.168.1.10: bytes=32 time=8ms TTL=64
Reply from 192.168.1.10: bytes=32 time=154ms TTL=64
Reply from 192.168.1.10: bytes=32 time=165ms TTL=64
Reply from 192.168.1.10: bytes=32 time=174ms TTL=64
Reply from 192.168.1.10: bytes=32 time=192ms TTL=64
Reply from 192.168.1.10: bytes=32 time=204ms TTL=64
Reply from 192.168.1.10: bytes=32 time=15ms TTL=64
Reply from 192.168.1.10: bytes=32 time=30ms TTL=64
Reply from 192.168.1.10: bytes=32 time=38ms TTL=64
Reply from 192.168.1.10: bytes=32 time=51ms TTL=64
Reply from 192.168.1.10: bytes=32 time=12ms TTL=64
Reply from 192.168.1.10: bytes=32 time=65ms TTL=64
Reply from 192.168.1.10: bytes=32 time=67ms TTL=64
Reply from 192.168.1.10: bytes=32 time=70ms TTL=64
Reply from 192.168.1.10: bytes=32 time=79ms TTL=64
Reply from 192.168.1.10: bytes=32 time=93ms TTL=64
Reply from 192.168.1.10: bytes=32 time=114ms TTL=64
Reply from 192.168.1.10: bytes=32 time=110ms TTL=64
Reply from 192.168.1.10: bytes=32 time=121ms TTL=64
Reply from 192.168.1.10: bytes=32 time=124ms TTL=64
Reply from 192.168.1.10: bytes=32 time=8ms TTL=64Ping statistics for 192.168.1.10:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 816ms, Average = 105msWhat is your CTS/RTS Threshold setting?
CTS/RTS Threshold for both 2.4 and 5GHz are the default, 2347.
