From: Roman Mamedov <rm@romanrm.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Luis Ressel <aranea@aixah.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Roman Mamedov <rm.wg@romanrm.net>
Subject: Re: Mixed MTU hosts on a network
Date: Sat, 14 Apr 2018 18:40:18 +0500 [thread overview]
Message-ID: <20180414184018.0166bc48@natsu> (raw)
In-Reply-To: <CAHmME9ru0iQeYMv_Y5dBZ1GoJvT_=UK8V74wWYNz2jtZWRFhfw@mail.gmail.com>
On Sat, 14 Apr 2018 15:16:56 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> Hi Roman,
>
> This commit should fix it. It now has a unit test too so that we don't
> hit this issue again. Thanks for reporting it in such detail.
>
> https://git.zx2c4.com/WireGuard/commit/?id=a88a067d5477f877003d3703bb3b95cb4e94bc46
>
> Let me know if that fixes it on your end.
>
> Jason
Thanks! I didn't get a chance to test it yet.
Leaving route MTUs aside, did you look into why the interface MTU of 1412
behaves erratically (while by all calculations it should just fit into 1492
underlying PPPoE MTU), with only 1408 working reliably? Is it also because of
the padding?
--
With respect,
Roman
next prev parent reply other threads:[~2018-04-14 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 9:25 Roman Mamedov
2018-03-16 9:35 ` Matthias Ordner
2018-03-16 10:53 ` Roman Mamedov
2018-03-16 16:20 ` Roman Mamedov
2018-03-16 10:01 ` Kalin KOZHUHAROV
2018-03-26 19:12 ` Luis Ressel
2018-04-14 1:38 ` Jason A. Donenfeld
2018-04-14 2:40 ` Jason A. Donenfeld
2018-04-14 13:16 ` Jason A. Donenfeld
2018-04-14 13:40 ` Roman Mamedov [this message]
2018-04-14 14:15 ` Jason A. Donenfeld
2018-04-14 14:38 ` Roman Mamedov
2018-04-14 14:45 ` Jason A. Donenfeld
2018-04-14 15:20 ` Roman Mamedov
2018-04-14 23:08 ` Jason A. Donenfeld
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=20180414184018.0166bc48@natsu \
--to=rm@romanrm.net \
--cc=Jason@zx2c4.com \
--cc=aranea@aixah.de \
--cc=rm.wg@romanrm.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).