From: Roman Mamedov <rm@romanrm.net>
To: blurt_overkill882@simplelogin.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] Header / MTU sizes for Wireguard
Date: Wed, 23 Aug 2023 21:15:44 +0500 [thread overview]
Message-ID: <20230823211544.7f3252ec@nvm> (raw)
In-Reply-To: <169230331253.7.2936868369217934671.167170975@simplelogin.com>
On Thu, 17 Aug 2023 20:14:52 +0000
blurt_overkill882@simplelogin.com wrote:
> I see here[1] that if you're using IPv4 exclusively, you can get away with
> an MTU of 1440. If my client only has IPv4 internet, however the server
> issues an IPv6 address for use by the client, can the client still use 1440
> without fragmentation, or must the client use 1420, because even though
> their connection is IPv4, they are issued an IPv6 address within the tunnel?
>
> [1] https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html
Yes they can. This is only affected by whether or not WG itself runs over
v4/v6, not whether you use v4 or v6 inside WG.
Be aware though that some residential Internet connections use MTU-reducing
tunnels for ISP authentication. The most popular one would be PPPoE with 8
bytes that you need to substract, but there also can be L2TP or PPTP with
larger overheads.
--
With respect,
Roman
next prev parent reply other threads:[~2023-08-23 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 20:14 blurt_overkill882
2023-08-23 16:15 ` Roman Mamedov [this message]
[not found] ` <CAC9cSOA4-NDcVNs6s_mMT8kp3J8apnCMEXFGx4_XokipABhmAQ@mail.gmail.com>
2023-08-24 13:21 ` Roman Mamedov
-- strict thread matches above, loose matches on Subject: below --
2016-07-26 19:42 jens
2016-07-26 23:41 ` Jason A. Donenfeld
2017-12-11 1:36 ` Jason A. Donenfeld
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=20230823211544.7f3252ec@nvm \
--to=rm@romanrm.net \
--cc=blurt_overkill882@simplelogin.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).