Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: j0eblack@teknik.io
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WIreGuard on embedded devices and traffic shaping question.
Date: Sat, 11 Feb 2017 10:20:08 +0100	[thread overview]
Message-ID: <CAHmME9pyHASJVx0ZC1GNLgddgF_Dja7bqRxGoML8hCuWLaPbzg@mail.gmail.com> (raw)
In-Reply-To: <91e1990891fb763b8090a2eed1321744@mail.teknik.io>

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@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

  reply	other threads:[~2017-02-11  9:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 11:05 j0eblack
2017-02-11  9:20 ` Jason A. Donenfeld [this message]
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=CAHmME9pyHASJVx0ZC1GNLgddgF_Dja7bqRxGoML8hCuWLaPbzg@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=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).