From: Roman Mamedov <rm@romanrm.net>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: wireguard@lists.zx2c4.com
Subject: Re: WireGuard Windows should have default MTU of 1280.
Date: Tue, 22 Feb 2022 02:44:43 +0500 [thread overview]
Message-ID: <20220222024443.1efe2c02@nvm> (raw)
In-Reply-To: <20220222005710.705a7023@nvm>
On Tue, 22 Feb 2022 00:57:10 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> On Mon, 21 Feb 2022 22:16:22 +0300
> Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> > 21.02.2022 22:11, Michael Adams wrote:
> > > Throwing in my two cents: I was using MTU 1280 on Tinc a few years back, for IPv6 VPN support on Windows & Linux. It's good practice.
> >
> > Lemme guess. The OP is routing wg packets over IPv6? Can this be
> > the problem here, because V6 has larger overhead so that 1420 is
> > too large to fit into 1500 bytes together with IPv6 header?
>
> 1420 is picked specifically so that it fits into a 1500 byte packet with IPv6.
>
> If you run WG exclusively over IPv4, you can use up to 1432.
Correction: 1440.
https://www.mail-archive.com/wireguard@lists.zx2c4.com/msg01856.html
I'm just used to subtracting 8 everywhere, because my ISP *does* use PPPoE. :)
--
With respect,
Roman
next prev parent reply other threads:[~2022-02-21 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 1:23 Rujbin
2022-02-21 18:52 ` tlhackque
2022-02-21 18:53 ` Michael Tokarev
[not found] ` <Mailbird-87f65eb5-1417-4955-ae28-858c7511900b@gmail.com>
2022-02-21 19:16 ` Michael Tokarev
2022-02-21 19:57 ` Roman Mamedov
2022-02-21 21:44 ` Roman Mamedov [this message]
2022-02-23 5:21 ` David Anderson
2022-02-21 19:18 ` Michael Tokarev
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=20220222024443.1efe2c02@nvm \
--to=rm@romanrm.net \
--cc=mjt@tls.msk.ru \
--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).