Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "M. Dietrich" <>
Subject: Behaviour on MTU problem
Date: Mon, 30 Aug 2021 20:43:03 +0200	[thread overview]
Message-ID: <1630347517.szy5mrrs16.astroid@morple.none> (raw)

Hi friends of Wireguard,

i am neither a network guru nor a kernel hacker and after all 
i had no time to fully investigate the case. so please read 
with a grain of salt.

i had my notebook in a wifi network lately that seemed to have 
some MTU size problems. download worked fine while uploads 
blocked for bigger packages. when i set the MTU down to 1200 
on the wg interface the same upload worked fine.

this was obviously a problem of that very wifi network and is
not related to wg at all, the dhcp answer did not even contain 
any MTU hints, so 1500 was assumed.

anyway the kernel locked up. commands like `ip` or `wg-quick 
down ...` get stuck and ^C oder even a `kill -9 ...` did not 
end the processes. any access to the wg interface blocked.

my question is if that scenario (misconfigured MTU size in the 
"outer network") is tested and works fine. i know that MTU 
size problem lead to lockups (that's why i immediatly came to 
that conclusion) but never saw such a hard lockup related to 
commands like `ip`.

if my assumption is just stupid let me know. if not i would 
further investigate the case, setup a test scenario and burn 
some time. what do you think?

best regards, michael

             reply	other threads:[~2021-08-30 18:43 UTC|newest]

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

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=1630347517.szy5mrrs16.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).