Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Dimitar Vassilev <dimitar.vassilev@gmail.com>
To: Derrick Lyndon Pallas <derrick@pallas.us>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard over WireGuard
Date: Tue, 12 May 2020 09:56:53 +0300	[thread overview]
Message-ID: <CAF+AZZULw_O3wjeEkSnWsXOKs_uddr9=a0-04OroKNhsSnKqSw@mail.gmail.com> (raw)
In-Reply-To: <f88c4fdf-ff31-a489-cb58-c02309016b13@pallas.us>

Hi all,

for my enlightenment can you please advise in which situation such
setups are useful?

Thanks!


На чт, 7.05.2020 г. в 4:01 Derrick Lyndon Pallas <derrick@pallas.us> написа:
>
> Note for the list: IPv6 has a minimum of 1280, which means 1360 in the
> outer layer. ~Derrick
>
>
> On 5/6/20 4:54 PM, Jason A. Donenfeld wrote:
> > On Wed, May 6, 2020 at 5:28 PM John Lauro <johnalauro@gmail.com> wrote:
> >> Wireguard is defaulting to 1420 MTU, the ethernet adapter is 1500 MTU,
> >> and I have IPv6 completely disabled.
> >>
> >> Can/should the MTU of wireguard be bumped to 1440?
> > You could if you wanted. But if you don't do it perfectly on all sides
> > with total uniformity and clearheadedness about your network design,
> > you'll run into subtle problems.

  reply	other threads:[~2020-05-12  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 16:57 Mo Balaa
2020-05-06 17:54 ` Derrick Lyndon Pallas
2020-05-06 21:37   ` Mo Balaa
2020-05-06 22:00     ` Jason A. Donenfeld
2020-05-06 22:24       ` Justin Kilpatrick
2020-05-06 22:25         ` Jason A. Donenfeld
2020-05-06 23:28           ` John Lauro
2020-05-06 23:54             ` Jason A. Donenfeld
2020-05-07  0:57               ` Derrick Lyndon Pallas
2020-05-12  6:56                 ` Dimitar Vassilev [this message]
2020-05-12 11:14                   ` Justin Kilpatrick
2020-05-31 19:34                     ` Mo Balaa

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='CAF+AZZULw_O3wjeEkSnWsXOKs_uddr9=a0-04OroKNhsSnKqSw@mail.gmail.com' \
    --to=dimitar.vassilev@gmail.com \
    --cc=derrick@pallas.us \
    --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).