Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "M. Dietrich" <>
To: Art Botterell <>,
Subject: Re: Behaviour on MTU problem
Date: Mon, 04 Oct 2021 07:30:44 +0200	[thread overview]
Message-ID: <1633325115.iotxkgm6j2.astroid@morple.none> (raw)
In-Reply-To: <>

Quotation from Art Botterell at August 30, 2021 21:55:
> One reads about fragmentation-induced failures and about 
> various MTU values that did or didn't work in a particular 
> situation.  [...]  what we could look out for in order 
> automatically to detect MTU issues [...] Is there some sort 
> of a ‘fragtest’ network utility out there?

My request was neither about anekdotic problems with different 
MTU sizes nor any automatic detection of a correct size and 
test utilities.

i was asking why the kernel module is completly locking up if 
a MTU size problem is present.

best regards, Michael

      reply	other threads:[~2021-10-04  5:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 18:43 M. Dietrich
2021-08-30 19:55 ` Art Botterell
2021-10-04  5:30   ` M. Dietrich [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1633325115.iotxkgm6j2.astroid@morple.none \ \ \ \

* 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).