From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: Dynamic routes
Date: Tue, 23 Nov 2021 22:40:06 +0000 [thread overview]
Message-ID: <edfa128e-7c6d-c329-5d63-4a3b32c2517c@york.ac.uk> (raw)
In-Reply-To: <3c70475b-64e5-acf7-819c-94f721fed8b6@gmx.net>
[-- Attachment #1.1: Type: text/plain, Size: 403 bytes --]
On 22/11/2021 17:20, Robert Dahlem wrote:
> The idea behind this is to have redundant tunnels. Let's say a Wireguard
> client has a preferred server and a secondary server. Packets should be
> routed through the preferred router while that tunnel is established and
> through the secondary server when the preferred server is not available
> for some reason.
Would route metrics work for this?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2021-11-23 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:20 Robert Dahlem
2021-11-23 22:40 ` Jonathon Fernyhough [this message]
2021-11-23 23:03 ` Robert Dahlem
2021-11-24 11:18 ` Chriztoffer Hansen
2021-11-24 12:04 ` Mike O'Connor
2021-11-24 15:07 ` Robert Dahlem
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=edfa128e-7c6d-c329-5d63-4a3b32c2517c@york.ac.uk \
--to=jonathon.fernyhough@york.ac.uk \
--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).