From: Robert Dahlem <Robert.Dahlem@gmx.net>
To: wireguard@lists.zx2c4.com
Subject: Dynamic routes
Date: Mon, 22 Nov 2021 18:20:12 +0100 [thread overview]
Message-ID: <3c70475b-64e5-acf7-819c-94f721fed8b6@gmx.net> (raw)
Hello,
I'm searching for a way to dynamically add or delete routes when a
tunnel comes up or goes down. I do not mean "interface wg0 comes up",
but explicitly "tunnel comes up" in the sense that both peers see each
other, key exchange has been successful and packets would be transported
through the tunnel.
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.
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.
Is there any way to react on tunnel state events in Wireguard?
Regards,
Robert
next reply other threads:[~2021-11-23 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 17:20 Robert Dahlem [this message]
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
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=3c70475b-64e5-acf7-819c-94f721fed8b6@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).