Development discussion of WireGuard
 help / color / mirror / Atom feed
From: John Lauro <johnalauro@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Justin Kilpatrick <justin@althea.net>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard over WireGuard
Date: Wed, 6 May 2020 19:28:46 -0400	[thread overview]
Message-ID: <CADGd2Dq3-EMBqA6bSKbR=C-pTZToPxv1xkM4BvYGh910T_e1Tg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rbKP4zB5nWG-9vf+2ZepXm+Gqii=qjQ8cnG0O+Dhu2tQ@mail.gmail.com>

Wireguard is defaulting to 1420 MTU, the ethernet adapter is 1500 MTU,
and I have IPv6 completely disabled.

Can/should the MTU of wireguard be bumped to 1440?

On Wed, May 6, 2020 at 6:26 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> On Wed, May 6, 2020 at 4:24 PM Justin Kilpatrick <justin@althea.net> wrote:
> >
> > > 1340 or 1360
> >
> > Why two options? I've been using 1340 for a long time.
>
> WireGuard over IPv4 has a 60 byte overhead. WireGuard over IPv6 has an
> 80 byte overhead.

  reply	other threads:[~2020-05-11  6:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 16:57 Mo Balaa
2020-05-06 17:54 ` Derrick Lyndon Pallas
2020-05-06 21:37   ` Mo Balaa
2020-05-06 22:00     ` Jason A. Donenfeld
2020-05-06 22:24       ` Justin Kilpatrick
2020-05-06 22:25         ` Jason A. Donenfeld
2020-05-06 23:28           ` John Lauro [this message]
2020-05-06 23:54             ` Jason A. Donenfeld
2020-05-07  0:57               ` Derrick Lyndon Pallas
2020-05-12  6:56                 ` Dimitar Vassilev
2020-05-12 11:14                   ` Justin Kilpatrick
2020-05-31 19:34                     ` Mo Balaa

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='CADGd2Dq3-EMBqA6bSKbR=C-pTZToPxv1xkM4BvYGh910T_e1Tg@mail.gmail.com' \
    --to=johnalauro@gmail.com \
    --cc=Jason@zx2c4.com \
    --cc=justin@althea.net \
    --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).