From: Derek Fawcus <dfawcus+lists-wireguard@employees.org>
To: Peter Linder <peter@fiberdirekt.se>
Cc: wireguard@lists.zx2c4.com
Subject: Re: potentially disallowing IP fragmentation on wg packets, and handling routing loops better
Date: Mon, 7 Jun 2021 12:58:29 +0100 [thread overview]
Message-ID: <YL4J5cFpPx1UTJbr@clarinet.employees.org> (raw)
In-Reply-To: <e86a2a76-1ff2-2272-f67b-555f36d8b444@fiberdirekt.se>
On Sun, Jun 06, 2021 at 01:14:16PM +0200, Peter Linder wrote:
> This would break things for me. We're doing a lot of L2 over L3 site to
> site stuff and we are using wireguard as the outer layer. Inner layer is
> vxlan or l2tpv3.
>
> In particular, people connect lots of stuff with no regard for MTU. For
> some things it's also very hard to change so we just assume people
> don't. Since the L3 network typically has the same MTU as the inner L2
> network, we need fragmentation. There is no practical way to be able to
> tell hosts on the L2 network about the limited mtu, for all we know they
> don't even run IP....
I've not looked in to vxlan much, but for L2TP you always have recourse
to RFC 4623, where the MRU & MRRU can be exchanged.
DF
next prev parent reply other threads:[~2021-06-07 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 9:13 Jason A. Donenfeld
2021-06-06 9:32 ` Nico Schottelius
2021-06-06 10:39 ` Vasili Pupkin
2021-06-06 11:14 ` Peter Linder
2021-06-07 11:58 ` Derek Fawcus [this message]
2021-06-06 19:03 ` Roman Mamedov
2021-06-06 22:33 ` Joe Holden
2021-06-07 9:34 ` Jason A. Donenfeld
2021-06-07 11:13 ` Roman Mamedov
2021-06-07 11:27 ` Jason A. Donenfeld
2021-06-07 11:46 ` Roman Mamedov
2021-06-07 11:55 ` Peter Linder
2021-06-07 18:50 ` Roman Mamedov
2021-06-07 11:18 ` Nico Schottelius
2021-06-09 23:26 ` Vasili Pupkin
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=YL4J5cFpPx1UTJbr@clarinet.employees.org \
--to=dfawcus+lists-wireguard@employees.org \
--cc=peter@fiberdirekt.se \
--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).