From: Barry Scott <barry@barrys-emacs.org>
To: Neal Becker <ndbecker2@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wireguard slow pings
Date: Sun, 16 Feb 2020 19:21:00 +0000 [thread overview]
Message-ID: <7304987A-6695-49A2-B9F1-AE4F13EBE2B9@barrys-emacs.org> (raw)
In-Reply-To: <CAG3t+pEeJ_+AUUoA3NvpKPhtp_-G78DJTS3PGZyRHigMCSHyww@mail.gmail.com>
[-- 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
next prev parent reply other threads:[~2020-02-23 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 12:58 Neal Becker
2020-02-16 19:21 ` Barry Scott [this message]
2020-02-23 14:52 ` Roman Mamedov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7304987A-6695-49A2-B9F1-AE4F13EBE2B9@barrys-emacs.org \
--to=barry@barrys-emacs.org \
--cc=ndbecker2@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).