Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Matthias Urlichs <matthias@urlichs.de>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Host routes – ARP on wireguard interfaces?
Date: Mon, 03 Dec 2018 15:14:06 +0200	[thread overview]
Message-ID: <87h8fukb1d.fsf@toke.dk> (raw)
In-Reply-To: <8f102b9a-c476-24b7-c800-d4abdb4318d1@urlichs.de>

Matthias Urlichs <matthias@urlichs.de> writes:

> 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?

I'm not sure I quite understand what it is you are trying to achieve;
why can't just you reconfigure the wireguard interface to route the IP
to the right peer?

-Toke
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2018-12-03 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03 12:02 Matthias Urlichs
2018-12-03 13:14 ` Toke Høiland-Jørgensen [this message]
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=87h8fukb1d.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=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).