From: Frank Volf <frank@deze.org>
To: lejeczek <peljasz@yahoo.co.uk>, wireguard@lists.zx2c4.com
Subject: Re: MTUs go strange ways - ?
Date: Mon, 4 Apr 2022 08:55:58 +0200 [thread overview]
Message-ID: <88efb74e-39ec-99e5-98a8-244e0af70724@deze.org> (raw)
In-Reply-To: <c8f39df3-e207-2dfb-c65d-5c6b4267f159@yahoo.co.uk>
Hi,
The "-s" option provides the length of the ICMP data in the packet, not
the total packet length.
To the data size you need to add 8 bytes for the ICMP header and 20
bytes for the IP header.
So, you are sending 1328 bytes (which is noted between the brackets in
your output).
If you change to "-s 1292" then you are actually sending packets with
total length of 1320.
Kind regards,
Frank
Op 2-4-2022 om 19:41 schreef lejeczek:
> 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.
>
prev parent reply other threads:[~2022-04-04 6:56 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
2022-04-03 20:14 ` Mark Lawrence
2022-04-04 6:55 ` Frank Volf [this message]
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=88efb74e-39ec-99e5-98a8-244e0af70724@deze.org \
--to=frank@deze.org \
--cc=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).