From: Roman Mamedov <rm@romanrm.net>
To: Saint Michael <venefax@gmail.com>
Cc: blurt_overkill882@simplelogin.com, wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] Header / MTU sizes for Wireguard
Date: Thu, 24 Aug 2023 18:21:11 +0500 [thread overview]
Message-ID: <20230824182111.4f92fdca@nvm> (raw)
In-Reply-To: <CAC9cSOA4-NDcVNs6s_mMT8kp3J8apnCMEXFGx4_XokipABhmAQ@mail.gmail.com>
On Thu, 24 Aug 2023 08:50:20 -0400
Saint Michael <venefax@gmail.com> wrote:
> This is the Achiles' heel of Wireguard. It reduces the MTU too much. Other
> tunneling techniques use a much larger MTU. I use Mikotik routers and one
> of the supported tunnels goes up to 1472. Some apps requiere a large MTU.
> Why Wireguard requieres so much space, so to speak?
Because it uses encryption, and each packet is also cryptographically signed.
I believe the other tunnels you have in mind will transfer data in plaintext
(unencrypted).
--
With respect,
Roman
next prev parent reply other threads:[~2023-08-24 13:23 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
[not found] ` <CAC9cSOA4-NDcVNs6s_mMT8kp3J8apnCMEXFGx4_XokipABhmAQ@mail.gmail.com>
2023-08-24 13:21 ` Roman Mamedov [this message]
-- 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=20230824182111.4f92fdca@nvm \
--to=rm@romanrm.net \
--cc=blurt_overkill882@simplelogin.com \
--cc=venefax@gmail.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).