From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Rémi Lapeyre" <remi.lapeyre@henki.fr>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: MTU on wireguard-apple for IPv6
Date: Thu, 19 Dec 2019 02:27:04 +0100 [thread overview]
Message-ID: <CAHmME9rKOd1rLygTtbho-vo85wQBGo5tQXdBrDvE-Fdk+r=_aw@mail.gmail.com> (raw)
In-Reply-To: <CA+jiYFD1SD-FgjgkwSTmkog1CYJYrEY87MKwD3StzAmmCJkn3w@mail.gmail.com>
On Thu, Dec 19, 2019 at 2:21 AM Rémi Lapeyre <remi.lapeyre@henki.fr> wrote:
> Does `networkSettings.tunnelOverheadBytes = 80` means the MTU will
> used be the one of the interface minus 80 bits of overhead for the
> WireGuard protocol?
Right, it means the MTU of the WireGuard interface will be the MTU of
your wifi interface minus 80.
> Some of our users where tethering over their phone connection so it
> seems that 1280 is appropriate in that case, but I’m confused as to
> why connections not going through the WireGuard tunnel where not
> impacted in that case.
Probably the phone's dhcp server doesn't pass the right MTU back to
the client, but then the phone does the mss-mtu hack to fix up TCP
connections. That hack doesn't work when the traffic is end-to-end
encrypted, as is the case with WireGuard, so no smaller MSS is ever
negotiated.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-12-19 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 18:26 MTU on wireguard-apple for IPv6 Rémi Lapeyre
2019-12-19 1:27 ` Jason A. Donenfeld [this message]
2019-12-19 10:37 ` Rémi Lapeyre
2019-12-27 16:10 ` Rémi Lapeyre
2019-12-18 10:41 Rémi Lapeyre
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='CAHmME9rKOd1rLygTtbho-vo85wQBGo5tQXdBrDvE-Fdk+r=_aw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=remi.lapeyre@henki.fr \
--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).