Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Luiz Angelo Daros de Luca <luizluca@gmail.com>
To: "Daniel Gröber" <dxld@darkboxed.org>
Cc: "Marek Küthe" <m-k-mailling-list@mk16.de>, wireguard@lists.zx2c4.com
Subject: Re: IPv6 and PPPoE with MSSFIX
Date: Wed, 23 Aug 2023 16:01:53 -0300	[thread overview]
Message-ID: <CAJq09z7Mm30aa5CTM0d+Vjb+KV9r+1uQbrGd6ZY-qB09Ng_0xw@mail.gmail.com> (raw)
In-Reply-To: <20230823171451.ld2fwslkl6blv6y2@House.clients.dxld.at>

> Hi,

Hi Daniel,

> On Wed, Aug 23, 2023 at 04:58:40PM +0200, Marek Küthe wrote:
> > PPPoE adds 8 bytes of overhead so that an MTU of 1432 can be used. I
> > also have to do this at home with my DSL line for example.
> > The MTU should be set on each side (on both peers) for this to work.
>
> Oh, I just realized I used the 1432 MTU in my earlier reply based on
> Marek's math but since Luiz's underlay network is IPv6 this is not actually
> correct. MTU=1440 is only correct on top of IPv4, for IPv6 the "optimal"
> MTU is 1420 so with PPPoE involved that's MTU=1412.
>
>   1500 Ethernet payload
>    -40 IPv6 header
>     -8 UDP header
>    -32 Wg header
>     -8 PPPoE
> ===================
>   1412 wg tunnel MTU

In my case, the PPPoE interface got MTU=1480. They might be stacking
something else on top of it or PPPoE might have optional fields. I
read somewhere that PPPoE might use either 8 or 20 bytes, but I'm not
an expert on PPPoE. If I don't control both sides, I would use 1400 by
default.

> --Daniel

  reply	other threads:[~2023-08-23 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 20:39 Luiz Angelo Daros de Luca
2023-08-23 14:58 ` Marek Küthe
2023-08-23 17:14   ` Daniel Gröber
2023-08-23 19:01     ` Luiz Angelo Daros de Luca [this message]
2023-08-23 20:47       ` Hugo Slabbert
2023-08-28 22:22         ` Luiz Angelo Daros de Luca
2023-08-23 17:07 ` Daniel Gröber
2023-08-23 19:55   ` Luiz Angelo Daros de Luca

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=CAJq09z7Mm30aa5CTM0d+Vjb+KV9r+1uQbrGd6ZY-qB09Ng_0xw@mail.gmail.com \
    --to=luizluca@gmail.com \
    --cc=dxld@darkboxed.org \
    --cc=m-k-mailling-list@mk16.de \
    --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).