From: Dave Taht <dave.taht@gmail.com>
To: "Ivan Labáth" <labawi-wg@matrix-dream.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] wg set - unexpected change of routes
Date: Tue, 30 Aug 2016 12:37:36 -0700 [thread overview]
Message-ID: <CAA93jw5vXAd4EKt089bu7NpCM4qv1YBdYChh_pwsoQK0-SQLew@mail.gmail.com> (raw)
In-Reply-To: <20160830192754.GA18189@matrix-dream.net>
I've only been using wireguard for 24 hours, and I like it a lot.
In my world, what I'd want is the ability to leverage source specific
routing, and to be able
to have nailed up dozens of routes to the same dozens of locations,
having a routing protocol layered on top to pick the best one (or, in
a tor-like way, pick a set of confusing ones), to ensure being able to
route around an outage somewhere.
prev parent reply other threads:[~2016-08-30 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 6:44 Ivan Labáth
2016-08-30 15:44 ` Bruno Wolff III
2016-08-30 19:27 ` Ivan Labáth
2016-08-30 19:37 ` Dave Taht [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=CAA93jw5vXAd4EKt089bu7NpCM4qv1YBdYChh_pwsoQK0-SQLew@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=labawi-wg@matrix-dream.net \
--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).