Very High Ping Times Default Gateway

I've finally got my R7800 with wireguard working as it should.
With the default gateway (wireguard) ping times were about 23ms using the tunnel, same kind of ping times as when I was running DD-WRT firmware.
Because I want my default route to be wan because I only have a few devices that require VPN. I inserted this option route_allowed_ips '0' in the network config file.
This worked and all traffic use the wan instead of the tunnel, however my ping times have shot up to 100ms. Can anyone provide some direction on where to look to see whats causing this?

Thanks

traceroute 8.8.8.8

mtr 8.8.8.8

ping 8.8.8.8 -c 5

I would think deprioritization of ICMP packets.

Thanks for your response here are my results minus the ip addresses:

Loss%   Snt   Last   Avg  Best  Wrst StDev
0.0%   140    1.4   1.4   0.9   2.3   0.3
0.0%   139   10.8  10.8  10.3  11.4   0.3
0.0%   139   11.6  11.4  10.6  12.9   0.4
0.0%   139   10.5  11.0  10.4  17.7   0.8
0.0%   139   13.8  13.6  13.1  14.4   0.3
0.0%   139   11.2  11.2  10.7  12.6   0.3
0.0%   139   12.3  12.4  11.5  20.5   1.3
0.0%   139   13.2  12.7  12.2  13.2   0.3


traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 46 byte packets
 1  xxxxxxx  0.931 ms  1.284 ms  1.413 ms
 2  xxxxxxx  10.572 ms  10.375 ms  10.316 ms
 3  xxxxxxx  11.686 ms  11.173 ms  11.707 ms
 4  xxxxxxx  10.485 ms  xxxxxxxxxx 10.342 ms  11.136 ms
 5  xxxxxxx  13.765 ms  13.538 ms  13.669 ms
 6  *  *  *
 7  dns.google (8.8.8.8)  13.008 ms  10.431 ms  10.370 ms
 
 PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=58 time=13.125 ms
64 bytes from 8.8.8.8: seq=1 ttl=58 time=12.952 ms
64 bytes from 8.8.8.8: seq=2 ttl=58 time=12.816 ms
64 bytes from 8.8.8.8: seq=3 ttl=58 time=12.657 ms
64 bytes from 8.8.8.8: seq=4 ttl=58 time=12.573 ms


These are the ping times which I am making my comparisons with:

Pinging google.com [2404:6800:4003:c1a::66] with 32 bytes of data:
Reply from 2404:6800:4003:c1a::66: time=97ms
Reply from 2404:6800:4003:c1a::66: time=97ms
Reply from 2404:6800:4003:c1a::66: time=98ms
Reply from 2404:6800:4003:c1a::66: time=97ms


I just reset my router and only setup a wan interface and performed a google.com ping as above and the ping was 11ms compared to 97ms.

Please use the "Preformatted text </>" button for logs, scripts, configs and general console output.
grafik
Please edit your post accordingly. Thank you! :slight_smile:

Do you have native IPv6 or some tunneling service?

Im not sure if you saw my post above I made some edits as I do further testing.
At the moment I reset my router and only have a wan interface and all ping times are normal. What do you mean as native IPv6? everything is stock. Im about to install wireguard again to see what happens.

I provided you an IPv4 address in Google-space to ping (i.e. 8.8.8.8). You pinged google.com and it resolved and used an IPv6 IP address (2404:6800:4003:c1a::66).

It seems your tests were done on IPv6. Given you have not clue what I'm asking, I assume it's native IPv6 - or in clearer terms IPv6 provided by your ISP.

It seems their IPv6 traffic has a little more latency.

you haven't by any chance disabled IPv4 on the LAN side ?

Try:

ping ipv4.google.com -c 4

ping ipv6.google.com -c 4

1 Like

I disabled Obtain IPv6 address in the wan advanced setup and my ping times are where they should be. Because I have no clue is it ok to do this? On my DD-WRT firmware IPv6 was also disabled.

No I havent disabled IPv4 on the Lan side.

Am I good to go from here?
Thanks

You should have left everything as is. Given your issue is solved, feel free to leave your configuration be.

Glad you solved your issue.

It seems you disabled your IPv6 service from the ISP.

I would advise ignoring "ping times" and focus on real experienced service and traffic quality.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.