From: lejeczek <peljasz@yahoo.co.uk>
To: wireguard@lists.zx2c4.com
Subject: MTUs go strange ways - ?
Date: Sat, 2 Apr 2022 18:41:12 +0100 [thread overview]
Message-ID: <c8f39df3-e207-2dfb-c65d-5c6b4267f159@yahoo.co.uk> (raw)
In-Reply-To: <c8f39df3-e207-2dfb-c65d-5c6b4267f159.ref@yahoo.co.uk>
Hi guys
I thought there was no better place to ask but here so -
both ends are centOS and end up having different MTUs for
'wg' interfaces and that I thought, was wrong.
1370 (server) VS 1320 (client)
I expected that would be negotiated between nodes without
user involved, right?
Moreover if I from the client do:
-> $ ping server -M do -s 1300
PING 10.3.3.1 (10.3.3.1) 1300(1328) bytes of data.
ping: local error: message too long, mtu=1320
Could some expert or two shed more light on what & why is
happening?
many thanks, L.
next parent reply other threads:[~2022-04-02 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c8f39df3-e207-2dfb-c65d-5c6b4267f159.ref@yahoo.co.uk>
2022-04-02 17:41 ` lejeczek [this message]
2022-04-03 20:14 ` Mark Lawrence
2022-04-04 6:55 ` Frank Volf
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=c8f39df3-e207-2dfb-c65d-5c6b4267f159@yahoo.co.uk \
--to=peljasz@yahoo.co.uk \
--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).