From: Matthias Urlichs <matthias@urlichs.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Host routes – ARP on wireguard interfaces?
Date: Mon, 3 Dec 2018 13:02:12 +0100 [thread overview]
Message-ID: <8f102b9a-c476-24b7-c800-d4abdb4318d1@urlichs.de> (raw)
Hi,
My problem: I have a couple of host routes within my network that point
to a service's "current master". When that machine goes down, I need to
automatically redirect its address to a different gateway. That's easy –
lookup the nexthop for the "real" server address and change the host
route – except when the destination is on wireguard and needs to be
(re)directed to a (different) peer.
My preferred solution for this (and also the one that is most intuitive
IMHO) would be some sort of pseudo-ARP – just enough to make "ip route
add FOO via BAR" work, 'BAR' being a host address that's associated with
exactly one wireguard peer.
Thoughts?
--
-- Matthias Urlichs
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2018-12-03 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 12:02 Matthias Urlichs [this message]
2018-12-03 13:14 ` Host routes – ARP on wireguard interfaces? Toke Høiland-Jørgensen
2018-12-03 13:49 ` Matthias Urlichs
2018-12-03 19:39 ` Toke Høiland-Jørgensen
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=8f102b9a-c476-24b7-c800-d4abdb4318d1@urlichs.de \
--to=matthias@urlichs.de \
--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).