Development discussion of WireGuard
 help / color / mirror / Atom feed
From: tlhackque <tlhackque@yahoo.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Question about MTU and Wireguard and the current changes
Date: Mon, 10 Jan 2022 15:56:07 -0500	[thread overview]
Message-ID: <f1444860-f37f-c268-1972-79dc31df2a9a@yahoo.com> (raw)
In-Reply-To: <1e345f21-4564-7df8-1aae-32ba14d42779@qupfer.de>


[-- Attachment #1.1: Type: text/plain, Size: 1369 bytes --]

On 10-Jan-22 15:37, henning.reich@gmail.com wrote:
> Hi,
> I run in some connection troubles between two wireguards host (one 
> running fedora 35, one arch linux). If I tried to transfer large files 
> through SSH (SCP or btrfs send/receive thorugh ssh through wireguard 
> tunnel) it stucks after a few byte and nothing transfered anymore.
>
> This happens in the last days, so probably an update on one or both 
> machines. I also saw, that there some changes on the MTU thing (If I 
> remember correctly, a per peer MTU is configurable)
>
> However. My first try was just set the MTU to a lower number (MTU = 
> 1200) and yes, scp works again.
> Okay, so I did the good old ping test. "ping -M do -s $SIZE -c 1 
> 172.16.0.2" with $SIZE increasing. And that surprised me. It works 
> until an Size of 36932 Bytes. Checked with wireguard and "MTU = 36932" 
> and yes, scp still working.
>
> Can somebody explain, why the old default setting of "65456" doesn't 
> work anymore but the MTU can set to much higher values as typical ones?
>
> Thanks
> Henning
>
Guess: Fragmentation happens somewhere and fragments are blocked at your 
router/firewall/host.  Blocking fragments is a common, if misguided, 
"security enhancement".

A packet trace would provide the necessary clues in any case.

Wireshark is a convenient way to get one.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

      reply	other threads:[~2022-01-10 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 20:37 henning.reich
2022-01-10 20:56 ` tlhackque [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=f1444860-f37f-c268-1972-79dc31df2a9a@yahoo.com \
    --to=tlhackque@yahoo.com \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: Question about MTU and Wireguard and the current changes' \
    /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

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