wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: StarBrilliant <coder@poorlab.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Fragmentation on UDP layer possible?
Date: Mon, 13 Aug 2018 16:53:41 +1000	[thread overview]
Message-ID: <CA+7UkwL94VsvX0aUJVejNT1JTdCKpOEFDibSwZKRatcPkQnCVA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oUWgtyBHK9WRT7oKe0Ud5ooTmGuOnkyMPRWpMBFGxV4Q@mail.gmail.com>

On Mon, Aug 13, 2018 at 4:41 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> WireGuard's socket.c calls udp_tunnel_xmit with the DF bit set to 0,
> which means if the underlying endpoint's path has an MTU that is too
> small, the UDP packet will simply be fragmented, not dropped.

Hi Jason,

Thank you for your answer.

Yes. This is how Wireguard handles fragmenting on IP layer. And thanks
to this feature I can build my network with high MTU inside.

For Roman Mamedov's question, I said there is such bug if you use
VXLAN inside Wireguard: You need to turn checksum offload off if
fragment is on.

But my doubt is "can we do fragment on UDP layer", or "on application
layer". That is because I found some public Wi-Fi simply does not
allow me to transmit any fragmented IP packets. Would you please
comment on this question? (For details, you may see my first post.)

Thanks!

      reply	other threads:[~2018-08-13  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-12 16:53 Fragmentation on UDP layer possible? StarBrilliant
2018-08-12 19:06 ` Roman Mamedov
2018-08-12 19:55   ` StarBrilliant
2018-08-14 10:29   ` Baptiste Jonglez
2018-08-14 20:26     ` Derek Fawcus
2018-08-13  6:40 ` Jason A. Donenfeld
2018-08-13  6:53   ` StarBrilliant [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=CA+7UkwL94VsvX0aUJVejNT1JTdCKpOEFDibSwZKRatcPkQnCVA@mail.gmail.com \
    --to=coder@poorlab.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).