Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: "WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Revisiting the weird MTU issue
Date: Wed, 10 Apr 2019 20:34:31 +0500	[thread overview]
Message-ID: <20190410203431.24b55c89@natsu> (raw)

Hello,

I use WireGuard over IPv6 on a PPPoE connection. The Internet interface MTU is
1492. By my calculations MTU 1412 on the WG interface should fit.

However, the following occurs on various MTU combinations between the Remote
(a server in a DC with full 1500 wire MTU) and Local WG interface MTUs:

Fails or not, is whether a within-WG Remote->Local TCP connection (iperf3)
works fine or hangs up after transferring a few initial bits of data.

Remote  Local  Result
====================
  1420   1420  Fails (as expected)

  1420   1412  Fails (weird)

  1412   1412  Works (fair enough)

  1420   1408  Works (super weird!!!)

Now I hope I described the situation clearer than the last time posting about
this, so maybe someone has an idea what could be the culprit?

So far this doesn't cause too much issue, as I'm using on designated p2p links
for when one of the peers is on this PPPoE, I just use 1412 on both sides. But
still, surely the above shouldn't happen?

-- 
With respect,
Roman
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2019-04-10 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 15:34 Roman Mamedov [this message]
2019-04-10 18:20 ` Derrick Lyndon Pallas

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=20190410203431.24b55c89@natsu \
    --to=rm@romanrm.net \
    --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).