NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
geogherkins1
Mar 30, 2022Tutor
AC1450 WNDR3700 WNDR4300 AP Mode Performance (Latency) Issue
Cable Modem >> AC1450 Router >> WNDR3700v4 AP I also have another WNDR4300SW AP (also connected to the AC1450), no issues noted, so problem seems to be the WNDR3700v4 while in AP mode. Sympt...
geogherkins1
Mar 30, 2022Tutor
Continuing to monitor whether an older firmware on WNDR3700v4 has a net positive impact.
Interesting idea on power supply.
If firmware doesn't fix it during the next 48 hours, I'll swap the AC-DC adapter between the WNDR4300SW and WNDR3700V4 and see if the symptom follows the power.
LOL The reason I've got old routers is they work, they are cheap, and no need to dump them in a landfill just because they are not shiny and new. My Windows 10 running on a Dell 530 desktop is over 14 years old still humming along great. ;/
plemans
Mar 30, 2022Guru - Experienced User
I hate throwing things in the garbage as well but going from a wireless N router to an decent AC or AX router would be a pretty solid wireless performance increase. N didn't have a whole lot of throughput. But if your speeds your ISP provides aren't that great.....older still works well.
- geogherkins1Apr 01, 2022Tutor
And now the mystery deepens. I have not had to swap power supplies, because the mystery symptom has moved to the other AP on its own accord.
As I implied, I have two APs connecting via wired 1GbE to a single router:
|
cable modem
24.183.35.241
|
|
AC1450 (Router) _ _ _ _ _ _ _ _ _ _ _ _ _
192.168.1.1 |
| | |
| PC1 |
| 192.168.1.20 |
| |
WNDR3700v4 (AP) |
192.168.1.2 |
| |
| |
PC2 WNDR4300SW (AP)
192.168.1.21 192.168.1.3
|
|
PC3
192.168.1.22
Depending on the font, that diagram will look ok or ugly. In Courier New (fixed font) it is beautiful!
When I opened this thread PC2 was suffering from too much jitter over wired and wireless.
I am focused entirely on wired network for troubleshooting.
Reply from 192.168.1.3: bytes=998 time=1277ms TTL=64
Reply from 192.168.1.3: bytes=998 time<1ms TTL=64
Reply from 192.168.1.3: bytes=998 time=1291ms TTL=64
Reply from 192.168.1.3: bytes=998 time<1ms TTL=64
Reply from 192.168.1.3: bytes=998 time=1291ms TTL=64Those results would be resolved by a power reset of the AP. Thinking it a firmware problem, I down-graded the firmware one release and waited over 48 hours. So far, no return of the symptom. But! Now the other WNDR4300SW AP, which up to now, so far as I know has not had this symptom, has shown the same jitter and every-other PING echo delay as did the first. PC3 now suffers the jitter problem.
So it would seem not to be a firmware problem with WNDR3700v4.
Of course, the common element here is router AC1400.
The change that exposed this issue was the introduction of the 2nd AP, WNDR4300SW to the network. (Previous to having a 2nd AP there was no jitter on WNDR3700v4).
Any more ideas?
- plemansApr 01, 2022Guru - Experienced User
did you check the primary router? What firmware is on it?
- geogherkins1Apr 03, 2022Tutor
Yes, as I stated opening this Q&A all routers have the most up-to-date firmware. The AC1450 is V1.0.0.36_10.0.17.
At the moment all three Netgear devices are returning a consistent <1ms PING from a 1472 byte payload (MTU 1500).
Pinging 192.168.1.3 with 1472 bytes of data
Reply from 192.168.1.3: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.3: bytes=1472 time<1ms TTL=64
Reply from 192.168.1.3: bytes=1472 time<1ms TTL=64I do not understand what exposes the firmware bug which results in inconsistent wired network performance. Just wishful thinking on my part that there is an easy fix. I'm continuing to monitor, but it becomes a troublesome issue in the middle of a workday when VPN clients and telework suddenly has awful jitter and can't be used until the router is powered off/on. I may have to replace the WNDR routers. The AC1450 seems stable enough.