From: Bruno <bruno@streamfeed.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Policy-based routing
Date: Sat, 14 Apr 2018 15:44:28 -0300 [thread overview]
Message-ID: <8108c2eb-e407-9d6d-4c0c-d26eb7a2bc93@streamfeed.com> (raw)
In-Reply-To: <CAHmME9r-ZHkhKjw+JTkF++t+9TBEnSv6AKF=FitQkg4V+a14dw@mail.gmail.com>
Hi Jason,
Thanks for your input. I agree with you.
But I could have the peers based on table routing and marking packets,
were all the traffic (0.0.0.0/0) would be routed based on the prior
conditions (tables and marking).
I'm doing one interface per peer right now, but I thought it could be
possible to achieve the same results with just one interface.
Bruno
On 04/13/2018 11:09 PM, Jason A. Donenfeld wrote:
> 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
prev parent reply other threads:[~2018-04-14 18:30 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
2018-04-14 18:44 ` Bruno [this message]
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=8108c2eb-e407-9d6d-4c0c-d26eb7a2bc93@streamfeed.com \
--to=bruno@streamfeed.com \
--cc=Jason@zx2c4.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).