From: jens <jens@viisauksena.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [fyi] test in the wild (wg + gretap + batman-adv) on tplink842
Date: Sun, 25 Dec 2016 05:14:47 +0100 [thread overview]
Message-ID: <1439626e-1f99-83fb-aab5-6a316346801e@viisauksena.de> (raw)
In-Reply-To: <1482597351.888073.828789001.771C92C9@webmail.messagingengine.com>
On 24.12.2016 17:35, Jehan Tremback wrote:
> Maybe I'm missing something obvious, but why would batman-adv affect th=
e
> speed?
not directly,
or i don't understand where your conclusion came from. batman-adv means
a lot of little batman-mesh-protocoll packets (namely ogm packets,
protocoll traffic is around 300 kbits in our network. which also will
travel over gretap/wireguard)
this scenario is equivalent to our free wifi network with 300++ nodes
and +-1000 users.
We use batman-adv as mesh protocol. While wireguard is layer 3 we need
to have layer2 over this tunnel.
so i tested wireguard + gretap + batman-adv successfully.
compared to a other known layer2 crypted tunnel protocol (fastd) this is
3 times faster, which is mainly due to wireguard is a kernel-module and
fastd lay in userspace. (-> context switche)
i testet on weak devices, because this is what is deployed in big
numbers in our (and many other) Freifunk community.
also there are plenty of packets and stuff - so this explain the
relative low throughput. At least compared with clean linked test-setups.=
hope this explain my motivation and the reason why i test this in this
special scenario.
Jens/fuzzle
--=20
make the world nicer, please use PGP encryption
next prev parent reply other threads:[~2016-12-25 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 0:24 jens
2016-12-24 16:35 ` Jehan Tremback
2016-12-25 4:14 ` jens [this message]
2016-12-30 1:24 ` Jehan Tremback
2016-12-31 2:30 ` 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=1439626e-1f99-83fb-aab5-6a316346801e@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).