From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bruno <bruno@streamfeed.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Policy-based routing
Date: Sat, 14 Apr 2018 04:09:17 +0200 [thread overview]
Message-ID: <CAHmME9r-ZHkhKjw+JTkF++t+9TBEnSv6AKF=FitQkg4V+a14dw@mail.gmail.com> (raw)
In-Reply-To: <a81edfe2-2a49-c49a-ea7c-65e60639ecfe@streamfeed.com>
Hi Bruno,
You can't set multiple peers to use 0.0.0.0/0 at the same time on the
same interface. How would it be able to choose which peer to send
traffic to then? Instead, if you want some kind of redundancy or
bonding, you can try using multiple interfaces, and then use whatever
traditional routing or load balancing tools that you ordinarily would.
Jason
next prev parent reply other threads:[~2018-04-14 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 19:38 Bruno
2018-03-09 21:35 ` Matthias Urlichs
2018-04-14 2:09 ` Jason A. Donenfeld [this message]
2018-04-14 18:44 ` Bruno
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='CAHmME9r-ZHkhKjw+JTkF++t+9TBEnSv6AKF=FitQkg4V+a14dw@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=bruno@streamfeed.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).