WIreGuard on embedded devices and traffic shaping question.

[j0eblack at teknik.io]

Thank you for the reply, Jason.

Indeed my email was a bit rushed, after some tweaking I was able to shape the entire 10.0.0.0/24 range since that is what I intend to use.

I used again tc and qdisk as in my previous projects and everything is working flawlessly, the website is open for users to add their public keys.

The next couple of days I have some free time and I will start a short white-up how new people can get WG going and eventually configure one of the peers to be a 'exit' point.

Thanks again for the awesome software!

Regards,
Joe

February 11, 2017 11:20 AM, "Jason A. Donenfeld" <Jason at zx2c4.com> wrote:
> Hey Joe,
> 
> Sorry for the late reply. There was a conference and then a small trip
> after, and now I'm catching up on the backlog.
> 
> On Fri, Jan 27, 2017 at 12:05 PM, <j0eblack at teknik.io> wrote:
> 
>> 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.
> 
> I'd certainly be interested in some sort of blog write-up. The more
> documentation and tutorials, the better, IMHO.
> 
>> 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?
> 
> The traffic shaping with WireGuard is the same trafic shaping found in
> the rest of the Linux kernel -- the qdisc and tc subsystem. I think
> you can use the usual techniques there for applying shaping to the
> entire interface or selectively to certain flows.
> 
>> 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?
> 
> I believe it can be using exactly that idea.
> 
> Regards,
> Jason