From: Robert Dahlem <Robert.Dahlem@gmx.net>
Cc: "WireGuard List (wireguard@lists.zx2c4.com)" <wireguard@lists.zx2c4.com>
Subject: Re: Dynamic routes
Date: Wed, 24 Nov 2021 16:07:22 +0100 [thread overview]
Message-ID: <f9e5c379-f199-e362-9ad7-3df580e45f93@gmx.net> (raw)
In-Reply-To: <3171350c-543d-92c9-c897-3cb752a811cf@pineview.net>
Hi,
On 24.11.2021 13:04, Mike O'Connor wrote:
> On 24/11/21 9:48 pm, Chriztoffer Hansen wrote:
>>> I could always install Quagga or Bird and use OSPF. But that might be a
>>> bit of an overkill for a simple active/passive failover.
>> RIP, OSPF, BGP, EIGRP. Either can work. And would IMO be sufficiently
>> simple to set up and maintain. Either way, you will need a daemon to
>> maintain monitoring of the packets being able to flow over the tunnel.
>> If you select a routing demon or another daemon. ... take a pick.
> Correct, not the job of Wireguard.
I can live with that. Thanks for clearing up.
Regards,
Robert
prev parent reply other threads:[~2021-11-24 15:07 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
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 [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=f9e5c379-f199-e362-9ad7-3df580e45f93@gmx.net \
--to=robert.dahlem@gmx.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).