Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Nicolai <nicolai-wireguard@chocolatine.org>
To: wireguard@lists.zx2c4.com
Subject: Re: best way for redundancy?
Date: Tue, 2 Mar 2021 17:10:21 +0000	[thread overview]
Message-ID: <20210302171021.GA65777@chocolatine.org> (raw)
In-Reply-To: <03ff01d70bbb$953d4750$bfb7d5f0$@lindenberg.one>

On Thu, Feb 25, 2021 at 10:17:06PM +0100, Joachim Lindenberg wrote:

> I do have a wireguard VPN that connects multiple sites. Unfortunately
> some routers are not available all the time, causing network disruption.
> I'd like to improve connectivity via redundancy, i.e. add multiple
> routers that connect the networks.

> What are the options to do that using wireguard? Can I have multiple
> peers with different keys and endpoint but same Allowed IPs? Will
> wireguard select the one available?

In the future I want a similar setup: multiple routers for each network
each seamlessly handling WireGuard when necessary.  I haven't put any
effort into this yet, but my general plan is to use CARP on OpenBSD,
with WireGuard sharing keys.  (I know you want distinct keys, so I
waited to respond until others had a chance.)  Anyway the routers in
City1 would share City1Keys, routers in City2 would share City2Keys,
etc.  When City1Router1 is unavailable, City1Router2 would grab the IP
address and be able to immediately speak WireGuard to the other
locations without anyone noticing.

https://www.openbsd.org/faq/pf/carp.html

Nicolai

  reply	other threads:[~2021-03-03  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 21:17 Joachim Lindenberg
2021-03-02 17:10 ` Nicolai [this message]
2021-03-04  8:58   ` AW: " Joachim Lindenberg

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=20210302171021.GA65777@chocolatine.org \
    --to=nicolai-wireguard@chocolatine.org \
    --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).