* MTUs go strange ways - ?
[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
0 siblings, 2 replies; 3+ messages in thread
From: lejeczek @ 2022-04-02 17:41 UTC (permalink / raw)
To: wireguard
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MTUs go strange ways - ?
2022-04-02 17:41 ` MTUs go strange ways - ? lejeczek
@ 2022-04-03 20:14 ` Mark Lawrence
2022-04-04 6:55 ` Frank Volf
1 sibling, 0 replies; 3+ messages in thread
From: Mark Lawrence @ 2022-04-03 20:14 UTC (permalink / raw)
To: lejeczek; +Cc: wireguard
On Sat Apr 02, 2022 at 06:41:12PM +0100, lejeczek wrote:
>1370 (server) VS 1320 (client)
>
>Could some expert or two shed more light on what & why is happening?
There is a (very small) clue in the name: Maximum *Transmission* Unit.
Routing between two IP addresses is not (necessarily) symetric: routes
are computed independently in each direction. So there is probably a
(1320 MTU) device somewhere inbetween which is only crossed by packets
in the client->server direction, but not in the reverse.
--
Mark Lawrence
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: MTUs go strange ways - ?
2022-04-02 17:41 ` MTUs go strange ways - ? lejeczek
2022-04-03 20:14 ` Mark Lawrence
@ 2022-04-04 6:55 ` Frank Volf
1 sibling, 0 replies; 3+ messages in thread
From: Frank Volf @ 2022-04-04 6:55 UTC (permalink / raw)
To: lejeczek, wireguard
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.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-04-04 6:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <c8f39df3-e207-2dfb-c65d-5c6b4267f159.ref@yahoo.co.uk>
2022-04-02 17:41 ` MTUs go strange ways - ? lejeczek
2022-04-03 20:14 ` Mark Lawrence
2022-04-04 6:55 ` Frank Volf
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).