WIreGuard on embedded devices and traffic shaping question.

j0eblack at teknik.io j0eblack at teknik.io
Fri Jan 27 12:05:21 CET 2017

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,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20170127/797488ae/attachment.html>

More information about the WireGuard mailing list