Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jehan Tremback <jehan@altheamesh.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [fyi] test in the wild (wg + gretap + batman-adv) on tplink842
Date: Sat, 24 Dec 2016 08:35:51 -0800	[thread overview]
Message-ID: <1482597351.888073.828789001.771C92C9@webmail.messagingengine.com> (raw)
In-Reply-To: <b9daea6b-caa1-6778-7236-02efb2288b99@viisauksena.de>

Maybe I'm missing something obvious, but why would batman-adv affect the
speed?

-- 
  Jehan Tremback
  jehan@altheamesh.com

On Fri, Dec 23, 2016, at 04:24 PM, jens wrote:
> i have done some testing with nodes configured like the one in the wild
> with a 842v3
> (similar to Tplink-841 but with 8Mb Flash, i have difficulties to build
> lede on the 841 - it is posible but extreme tricky, so for now i needed
> a PoC of wireguard with gretap to use batman-adv routing protocol)
> 
> results are, with nearby all the packages we use in the wild for our 350
> Node Meshnetwork.
> link only      - 32 Mbit
> on top wg0 - 26,7 Mbit
> on top gretap and batman-adv (v14) - 14,8 Mbit.
> 
> lede - gluon with Wireguard 0.0.161223 kernel 4.4.36
> 
> i described it a bit more in detail here (sorry only in german)
> https://forum.freifunk.net/t/erste-ernuechternde-lede-wireguard-gretap-ergebnisse-unter-livebedingungen/14057
> 
> so, just to let you know. thx and have some nice days
> Jens
> 
> -- 
> make the world nicer, please use PGP encryption
> 
> 
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2016-12-24 16:28 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 [this message]
2016-12-25  4:14   ` jens
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=1482597351.888073.828789001.771C92C9@webmail.messagingengine.com \
    --to=jehan@altheamesh.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).