From: Roman Mamedov <rm@romanrm.net>
To: Harald Dunkel <harri@afaics.de>
Cc: wireguard@lists.zx2c4.com
Subject: Re: mtu on Linux vs MacOS
Date: Fri, 22 Jan 2021 03:09:35 +0500 [thread overview]
Message-ID: <20210122030935.3f8bba00@natsu> (raw)
In-Reply-To: <20210121190718.13465dea@natsu>
On Thu, 21 Jan 2021 19:07:18 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> On Sun, 17 Jan 2021 11:36:42 +0100
> Harald Dunkel <harri@afaics.de> wrote:
>
> > Hi folks,
> >
> > I am using PPPoE to connect to my IP provider. To use wireguard on Linux I
> > have to reduce the MTU in wg0.conf to 1400. Using the default 1420 a ssh
> > connection tunneled through wireguard gets stuck (reproducible). An echo
> > of a very long line (e.g. 4096 chars) is sufficient.
> >
> > The weird part is, MTU 1420 works fine for wireguard on MacOS. How comes
> > that Wireguard appears to be more stable on MacOS than on Linux?
>
> WireGuard works just fine for me on Linux using MTU 1432 if over IPv4, and
> 1412 if over IPv6. The underlying PPPoE device MTU is 1492 in my case. Check
> which PPPoE MTU you use in Linux vs in MacOS.
>
Oh, and I just remembered -- you're better off setting the same MTU on the
entire WG network, i.e. substract those 8 bytes of PPPoE interface on the
remote host's WG interface as well. Else the local interface MTU will need a
weird and so far unexplained further 4-byte reduction for things to work:
https://lists.zx2c4.com/pipermail/wireguard/2019-April/004078.html
--
With respect,
Roman
prev parent reply other threads:[~2021-01-21 22:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 10:36 Harald Dunkel
2021-01-21 14:07 ` Roman Mamedov
2021-01-21 22:09 ` 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=20210122030935.3f8bba00@natsu \
--to=rm@romanrm.net \
--cc=harri@afaics.de \
--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).