From: j0eblack@teknik.io
To: wireguard@lists.zx2c4.com
Subject: WIreGuard on embedded devices and traffic shaping question.
Date: Fri, 27 Jan 2017 11:05:21 +0000 [thread overview]
Message-ID: <91e1990891fb763b8090a2eed1321744@mail.teknik.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
Greetings people and robots,
I'm sending this email with a positive feed-back of my experience with WireGuard and the embedded device that I used with it, also I want to thank the WireGruard dev team for the awesome free software!
WireGuard is running on a Olimex Lime A-10 board with Debian Jessie on it:
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.6 (jessie)
Release: 8.6
Codename: jessie
uname -a
Linux lime-a10 4.8.4-sunxi #6 SMP Sun Oct 23 15:55:47 CEST 2016 armv7l GNU/Linux
The WireGuard packages were installed from the sid repo, everything went smoothly without any manual intervention for the setup.
My initial idea was to use WireGuard as a open-vpn-type server-client setup.
After reading some of the mails from this list I was able to get two peers to talk to each other and after that is was a matter of iptables rules to get one of the peers to act as a 'exit server' and the other connected peers to it as 'clients'.
If anyone is interested in this set-up I can write a short guide how you can achieve that and other people can point if any mistakes were made during the setup.
Something that I want to do, and I was not able to find information about it in the mailing list or the docs on the website is, can bandwidth (traffic shaping) limits be applied between connected peers?
I have done this in the past with open-vpn and tc (per IP address shaping) and I am really curious if this can be done inside WireGuard or not?
With regards,
j0eblack
[-- Attachment #2: Type: text/html, Size: 1908 bytes --]
next reply other threads:[~2017-01-27 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 11:05 j0eblack [this message]
2017-02-11 9:20 ` Jason A. Donenfeld
2017-02-13 13:37 ` j0eblack
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=91e1990891fb763b8090a2eed1321744@mail.teknik.io \
--to=j0eblack@teknik.io \
--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).