Tried my AX58U again, unplugged from anything LAN related, WAN, etc. From this room through the wall where it was before, where the AX6000 is now, I get almost, slightly better results with smaller spikes. If I enter the room/hallway, I get 2-3ms constant, no spikes. AX6000 was turned off at this time to prevent interference.
I've literally disabled all beamforming, air fairness, switches to AC 20MHz on my AX6000, changed the firmware to try avoid that case too, and... nope. Close proximity, 2-3 meters from the router, no obstacles, I still get 2-6ms at least. There are spikes when there's the wall though, and they're higher than AC, up to a few tens of ms, but rarely.
There's literally nothing more I can do. I can't isolate the interference in the middle of downtown apartment. In 2 weeks I'll travel to the countryside to relax a bit and bring the router with me, there's a house each hundred meters, that should be enough to test interference - though there are HV power lines near, but it's as much as I can do.
Sanity sake, I went and changed all professional settings on 5GHz on both firmwares, rebooted the device after for it to surely apply, and there's still the added latency. This is what my ping test looks like, one wall, and all the above settings:
Code:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 6ms, Average = 3ms
I gave a test without spikes to 50-60ms that sometimes happen as it's unknown why and pretty rare, 2 requests one by one, each 100 reqs.
This is to the HGW/modem on the WAN port:
Code:
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=8ms TTL=63
Reply from 192.168.0.1: bytes=32 time=6ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=5ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=5ms TTL=63
Reply from 192.168.0.1: bytes=32 time=28ms TTL=63
Reply from 192.168.0.1: bytes=32 time=6ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=7ms TTL=63
Reply from 192.168.0.1: bytes=32 time=6ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=5ms TTL=63
Reply from 192.168.0.1: bytes=32 time=5ms TTL=63
Reply from 192.168.0.1: bytes=32 time=3ms TTL=63
Reply from 192.168.0.1: bytes=32 time=4ms TTL=63
Reply from 192.168.0.1: bytes=32 time=5ms TTL=63
Ping statistics for 192.168.0.1:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 28ms, Average = 5ms
So it's official, LAN ping is going to be 3-8ms with this guy. Next test is ping/traceroute to 8.8.8.8 with both routers and check how they compare. I might do it on the exit of the ISP hop/gateway to avoid aditional jitter that their equipment may add. I'm on broadband/DOCSIS on 400/40, can get 1000/500 for the same price but there are some things that come along with it that are turn offs for now. So DOCSIS alone isn't that stable (packet story, ask to deliver, then deliver, then ask if delivered... latency nightmare) so I'll try to avoid it as much as possible.
Any AX6000 owners out there that might test their WIFI local ping times to the router? I'm trying to accept this as normal behaviour but if you guys think it's not and someone else with the same router can say they have the same issues, no point of replacing the unit.
Also, I can't find any beta firmware for it.
