From: Roman Mamedov <rm@romanrm.net>
To: Neal Becker <ndbecker2@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wireguard slow pings
Date: Sun, 23 Feb 2020 19:52:25 +0500 [thread overview]
Message-ID: <20200223195225.6210b37f@natsu> (raw)
In-Reply-To: <CAG3t+pEeJ_+AUUoA3NvpKPhtp_-G78DJTS3PGZyRHigMCSHyww@mail.gmail.com>
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
prev parent reply other threads:[~2020-02-23 14:52 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
2020-02-23 14:52 ` Roman Mamedov [this message]
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=20200223195225.6210b37f@natsu \
--to=rm@romanrm.net \
--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).