From: jens <jens@viisauksena.de>
To: wireguard@lists.zx2c4.com
Subject: [WireGuard] Header / MTU sizes for Wireguard
Date: Tue, 26 Jul 2016 21:42:41 +0200 [thread overview]
Message-ID: <62f0dc7c-4eb4-523a-c548-ee2b2a6ec038@viisauksena.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
hi,
we are succesfully built an alternative for our tincd backbone with
wireguard (and on top l2tpv3/batv15).
with iperf we get up to 500Mbs on l2tpv3 level.. (upto 700 on pure
wireguard)
for optimization we need to know more and better about the used header,
the possible data-size per packet-header to increase throuhput with all
the other layers.
Do you know your headersize, or some more easy details in
headersize/packetsize...
where does the default mtu of 1423 come from
thx jens
--
make the world nicer, please use PGP encryption
[-- Attachment #2: Type: text/html, Size: 893 bytes --]
next reply other threads:[~2016-07-26 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 19:42 jens [this message]
2016-07-26 23:41 ` Jason A. Donenfeld
2017-12-11 1:36 ` Jason A. Donenfeld
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
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=62f0dc7c-4eb4-523a-c548-ee2b2a6ec038@viisauksena.de \
--to=jens@viisauksena.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).