From: John Huttley <john@mib-infotech.co.nz>
To: wireguard@lists.zx2c4.com
Subject: MTU
Date: Sun, 18 Dec 2016 18:33:19 +1300 [thread overview]
Message-ID: <1d684ee8-9f6c-a9f0-4cec-df0116cb97b7@mib-infotech.co.nz> (raw)
In-Reply-To: <CAHmME9o_BzZRj2HVpQMUxE7t1DS_NcHJWXe8zsvndNbwu+j+Qg@mail.gmail.com>
Hi,
Did we have to configure our interfaces with a reduced MTU (1417) after
this last update?
I've getting results reminiscent of the need for MSS clamping.
Connects ok, timeouts on transfer etc.
--John
next prev parent reply other threads:[~2016-12-18 5:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 16:09 CodeBlue WireGuard Talk Now Online Jason A. Donenfeld
2016-12-18 5:33 ` John Huttley [this message]
2016-12-18 18:04 ` MTU 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=1d684ee8-9f6c-a9f0-4cec-df0116cb97b7@mib-infotech.co.nz \
--to=john@mib-infotech.co.nz \
--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).