wireguard slow pings

wireguard slow pings

[Neal Becker]

[-- Attachment #1.1: Type: text/plain, Size: 847 bytes --]

I'm testing wireguard
wireguard-0.0.20191219-2.fc31.x86_64
between a Fedora 31 client and server, comparing to openvpn.

Openvpn is running between a linux client outside my lan and a server on my
router, which is running dd-wrt.
I'm pinging between that linux client and another linux client within my
lan.

wireguard is running between the same linux client outside my lan and the
same other linux client within my lan.  This
time router is simply forwarding packets via NAT.

Openvpn ping times are much lower (about 10ms) and much lower variance than
wireguard.  Wireguard pings
are all over the place.

Packets coming in from the WAN are traversing some firewall that I don't
control, which may be affecting results.  Openvpn
is config to use udp.

Any ideas?

Thanks,
Neal

-- 
*Those who don't understand recursion are doomed to repeat it*

[-- Attachment #1.2: Type: text/html, Size: 1240 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: wireguard slow pings

[Barry Scott]

[-- Attachment #1.1: Type: text/plain, Size: 1548 bytes --]



> On 16 Feb 2020, at 12:58, Neal Becker <ndbecker2@gmail.com> wrote:
> 
> I'm testing wireguard
> wireguard-0.0.20191219-2.fc31.x86_64 
> between a Fedora 31 client and server, comparing to openvpn.
> 
> Openvpn is running between a linux client outside my lan and a server on my router, which is running dd-wrt.
> I'm pinging between that linux client and another linux client within my lan.
> 
> wireguard is running between the same linux client outside my lan and the same other linux client within my lan.  This
> time router is simply forwarding packets via NAT.
> 
> Openvpn ping times are much lower (about 10ms) and much lower variance than wireguard.  Wireguard pings
> are all over the place.
> 
> Packets coming in from the WAN are traversing some firewall that I don't control, which may be affecting results.  Openvpn
> is config to use udp.
> 
> Any ideas?

I can think of two ways to investigate this.

Use tcpdump on the router to see the timing of the packets on the wg0 device.
How quickly do you see the ICMP echo get answered?

Use traceroute from the outside to find the ping times of all the hops on the path.
Is there a significant difference between the ping time on the edge of the router
and the wg0 device ping time?

Barry

> 
> Thanks,
> Neal
> 
> -- 
> Those who don't understand recursion are doomed to repeat it
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard


[-- Attachment #1.2: Type: text/html, Size: 2933 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

Re: wireguard slow pings

[Roman Mamedov]

On Sun, 16 Feb 2020 07:58:48 -0500
Neal Becker <ndbecker2@gmail.com> wrote:

> I'm testing wireguard
> wireguard-0.0.20191219-2.fc31.x86_64
> between a Fedora 31 client and server, comparing to openvpn.
> 
> Openvpn is running between a linux client outside my lan and a server on my
> router, which is running dd-wrt.
> I'm pinging between that linux client and another linux client within my
> lan.
> 
> wireguard is running between the same linux client outside my lan and the
> same other linux client within my lan.  This
> time router is simply forwarding packets via NAT.
> 
> Openvpn ping times are much lower (about 10ms) and much lower variance than
> wireguard.  Wireguard pings
> are all over the place.
> 
> Packets coming in from the WAN are traversing some firewall that I don't
> control, which may be affecting results.  Openvpn
> is config to use udp.
>
> Any ideas?

Did you try using the same port for WG, as you use for OpenVPN (of course
stopping OpenVPN for a while to try that)?

It is possible that ISPs employ different priorities for particular UDP port
ranges;

Or they might do load-balancing across multiple links by src/dst/port/protocol,
and your WG's combination of that randomly happens to go via some unlucky
overloaded one.

-- 
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard