wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Pippin Wallace <pwallace@figure.com>
To: wireguard@lists.zx2c4.com
Subject: More MTU questions
Date: Fri, 14 Dec 2018 11:23:20 -0700	[thread overview]
Message-ID: <CAHj=41oohTckRQvNvi_6v-0BhaUmFyNv6+7O-TxRTgoWVCJYtA@mail.gmail.com> (raw)


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

WG List,

I have read the previous posts in the archive that mentioned MTU but did
not derive an answer to the following.

I had a frame length of 1474 try to transit WG and it sent back a ICMP
"fragmentation needed" but the source would not fragment the packet.  So I
upped the wg0 MTU to 1488, which worked for this frame, but saw all the
notes about the going over 1440 for IPv4 traffic may cause problems.

What is the best approach to deal with this problem?  I read about MSS
clamping but am not sure this will work or is the best first approach.

I am out of my depth with this at present and could really use some advice
from this expert group.

If I just need to read an RFC or other doc would you please point me in the
right direction?

Sincere regards,

Pippin

-- 
This message and its contents are confidential. If you received this 
message in error, do not use or rely upon it. Instead, please inform the 
sender and then delete it. Thank you.

[-- Attachment #1.2: Type: text/html, Size: 1223 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

                 reply	other threads:[~2019-01-02 18:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAHj=41oohTckRQvNvi_6v-0BhaUmFyNv6+7O-TxRTgoWVCJYtA@mail.gmail.com' \
    --to=pwallace@figure.com \
    --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).