NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Arkkady
May 23, 2019Aspirant
Horrible intermittent latency on the orbi router
Hello everyone,
I have had my orbi for a year now, and have loved every minute of it! Aside from a few intial issues with some of my smart home devices. I was able to iron those out, and I ha...
Arkkady
May 23, 2019Aspirant
Thank you both for your replies!
The Firmware was recently automatically updated to the latest 2.3.1.60 firmware on both Satellite and router.
The router has been tested in both AP and Router Mode, with the same results. At this time however, the router and satellite have been placed back into router mode.
The ISP modem is not connected to this network at this time, as this is currently being used for point to point communication within the home. ( due to the issues I suddenly started having)
The home is approximately 2700 sqft. The Satellite had been located approximately 40 ft from the router with no issues for over 12 months.
However during troubleshooting this was tested at various lengths, measured out for consistency,
Tested using ethernet back haul directly next to each other, and at 10 ft, 20 ft 25 ft , 30 ft, and 40 ft with the same results.
Additionally tested with wireless back haul measure out in the same increments: 10 ft, 20 ft 25 ft , 30 ft, and 40 ft with the same results.
I was able to replicate the results using just the router between wired device and wireless devices.
Several Computers where used for testing.
2 windows based machines running windows 10 both with Wireless cards and wired gigabit ethernet ports.
2 Linux Based machines with wireless and gigabit ethernet cards.
This allowed me to confirm the same latency spikes occur regardless of a mix between wired wireless windows only, Linux only, and a windows / Liinux mix.
Each test was completed on the windows machines using the cmd prompt for simple ping testing, and win mtr for dynamic trace route results. All showing latency spikes above 3000 ms.
On the linux machine, I used the natively supported MTR and ping tools within the OS to the same result in all scenarios.
I have attempted to use all optional channels available for both 2.5 and 5ghz channels, and have toggled all available settings, such as: AP/Router mode, Beam Forming, MIMI, Daisy Chain, Fast Roaming, and unchecked the 20/40 MHZ Coexistence box.
I have rebooted the router and satellite several times, I have pin hole reset for 60/90/120 seconds the router and satellite to no avail.
I have also downgraded the firmware on both the router and satellite, which prompted the auto update, and I am still experiencing latency spikes across the LAN when isolated from the carrier Modem.
As far as the Neighboring Wifi, I have not seen any new wifi networks set up in the area, and since I am in an "established neighborhood" I am surrounded by retirees.
While the carrier modem is not in the topography at the moment, I have had the carrier Spectrum come out and replace the modem several times.
This was done in the beginning as I had initially suspected the WAN connection to be causing the latency spikes as they were originally observed while a member of the house hold was gaming.
The modems used, all of which produced the same results where: Hitron, Technicolor, Cisco, and Ubee.
I am currently using the UBEE, When initially troubleshooting the carrier modem I ensured that each device had, Wireless, firewall, and SIP ALG disabled.
All signal levels on all carrier channels in the modem are within spec:
Currently:
Downstream SNR: 39 dB
Upstream SNR: 38 dB
Downstream Power: 0.1 dBmv ( Dang near perfect)
Upstream Power: 41 dBmv ( again excellent)
No T3 or T 4 timeouts observed.
As you can see I have been working on this for a bit, and have tried to be as systematic in my testing as possible.
A shame that one of the best routers I have ever seen has suddenly stopped working after 12 months of flawless operation.
Any help would be greatly appreciated.
CrimpOn
May 23, 2019Guru - Experienced User
Arkkady wrote:Each test was completed on the windows machines using the cmd prompt for simple ping testing, and win mtr for dynamic trace route results. All showing latency spikes above 3000 ms.
Thanks for the details... a LOT of effort. Some questions:
- What is the average (typical) ping response time
- How often do these 3,000ms responses occur? (every 5 minutes? once an hour?)
- Is there a regular pattern to the long responses?
- How many long responses in a row? (only one, several?)
- Are the ping tests all run from the same machine, using other computers for response?
I configured some ICMP tests between Windows & Linux machines, also connected via ethernet & WiFi (all 5G now that I think of it). Two Windows 7 desktops, one Windows 10 laptop, Linux Mint on a laptop, and Raspberry pi3b+. My favorite tool is "hrping" for Windows because it reports in fractions of ms (not terribly significant when one is observing 3,000ms). I typically generate 5,000 ICMP requests which takes about 83 miinutes. When any WiFi exists in the connection (to the device or satellite backhaul), responses are on average longer and maximum response time is higher. Everything wired is always faster.
In all those tests, ping responses are nearly always between 2 and 7ms. The longest responses were from the Windows 10 laptop over 5G WiFi at 116 and 218 ms, but even then 95% of those responses were under 12ms. In all of my testing, I never had a ping response over 250ms. Not once.
I am absolutely convinced that what you observe is indeed happening. Since it appears not to happen to me, there must be something different between our installations.
- ArkkadyMay 25, 2019Aspirant
This is part of an output from a ping test thats pretty indicative of what I am seeing. completely Sporadic and random Latency Spikes. This is actually when the network is at its best now. As you can see, I used to get EXCELLENT response time from the network for over 12 months. and now its riddled with ping spikes...
the latency doesnt change if its simply from one pc to another, whether that be a mix of wired/wireless or wired/wired from same router or wired router to wired satellite, or Wireless to Wireless.
As you can see in the quick example below, wired windows pc to router, it is usually one packet alone at most 5 or 7 in a row.
ping 8.8.8.8 -n 10000
Pinging 8.8.8.8 with 32 bytes of data
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=40ms TTL=52
Reply from 8.8.8.8: bytes=32 time=294ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=19ms TTL=52
Reply from 8.8.8.8: bytes=32 time=42ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=21ms TTL=52
Reply from 8.8.8.8: bytes=32 time=19ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=21ms TTL=52
Reply from 8.8.8.8: bytes=32 time=21ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=29ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=31ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=30ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=530ms TTL=52
Reply from 8.8.8.8: bytes=32 time=27ms TTL=52
Reply from 8.8.8.8: bytes=32 time=20ms TTL=52
Reply from 8.8.8.8: bytes=32 time=20ms TTL=52
Reply from 8.8.8.8: bytes=32 time=1420ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=28ms TTL=52
Reply from 8.8.8.8: bytes=32 time=25ms TTL=52
Reply from 8.8.8.8: bytes=32 time=2543ms TTL=52
Reply from 8.8.8.8: bytes=32 time=25ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=22ms TTL=52
Reply from 8.8.8.8: bytes=32 time=34ms TTL=52
Reply from 8.8.8.8: bytes=32 time=28ms TTL=52
Reply from 8.8.8.8: bytes=32 time=419ms TTL=52
Reply from 8.8.8.8: bytes=32 time=24ms TTL=52
Reply from 8.8.8.8: bytes=32 time=23ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=26ms TTL=52
Reply from 8.8.8.8: bytes=32 time=38ms TTL=52
Reply from 8.8.8.8: bytes=32 time=25ms TTL=52
Reply from 8.8.8.8: bytes=32 time=3123ms TTL=52- CrimpOnMay 25, 2019Guru - Experienced User
Thanks for the data. And, yes, this is ghastly. In order to tie this phenomenon to the Orbi, the ping target has to be local. Otherwise, there is a lot of equipment between the Orbi and 8.8.8.8. Can you show a sample of one computer to another computer within the LAN?
- ArkkadyMay 25, 2019Aspirant
I know it was a book, sorry about that, but its the exact same.
a mirror image
There would be no serviceable reason to conduct that test again for teh 10th time. As there is no new info to obtain from a screen shot such as that. just imagine an internal IP address..
And I have no doubt its the orbi as the same machines on the carrier modem wifi shows no latency spikes.
Note: the carrier modem wifi was disabled prior to this point to avoid causing wifi interference.
Not to mention the carrier modem has a weaker signal, with no repeaters in the same wifi environment
Anyone have any suggestions on how to resolve a clear problem withe the wifi from the orbi system. Im sorry but with all the work done to isolate the issue it is CLEARLY the orbi.