From: Dashamir Hoxha <dashohoxha@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Using Wireguard for Geo redundancy
Date: Wed, 4 Nov 2020 17:53:25 +0100 [thread overview]
Message-ID: <CAMucfLxWUdzx5LfiYRhE+yypY8zC6ch868RO_NV231GCMvZo6Q@mail.gmail.com> (raw)
In-Reply-To: <1604430353.311423080@webmail.emailsrvr.com>
On Tue, Nov 3, 2020 at 8:07 PM dxiri@xirihosting.com
<dxiri@xirihosting.com> wrote:
>
> Hi!
>
> I am looking for information on how to leverage Wireguard in a geo-redundancy scenario.
>
> We have a couple management boxes colocated next to each other that provide HA via a VIP that "jumps" between each of those management boxes depending on availability.
How is HA implemented in this case? If it is based on ARP, then I am
afraid that WireGuard cannot do the same thing.
>
> Now lets say we want to place management box on datacenter 1 (DC1) and management box 2 on datacenter2 (DC2).
>
> Assuming the VIP cannot move between DCs, how could you leverage Wireguard to provide the same level of redundancy but with geographically dispersed hosts?
>
> Any information on this topic or documentation that points me in the right direction would be really appreciated!
Here are some of the cases where WG can be useful:
https://gitlab.com/docker-scripts/wireguard/-/blob/master/docs/wg-usecases.md
None of them solves your problem, but maybe this can help you to
understand better how WG works.
>
> Thanks!
> Diego
>
next prev parent reply other threads:[~2020-11-09 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 19:05 dxiri
2020-11-04 11:11 ` Laura Smith
2020-11-04 16:53 ` Dashamir Hoxha [this message]
[not found] ` <gBLFnYn1ENCoAu8pZXEVAFF88CT1DSPAOnmcV47vBrvQlLpA1jg2Yp6iZb9RotAOGDJPrqgeD iqOxesYB09WPXEtWsqR5R5rvx-udouR9-w=@protonmail.ch>
[not found] ` <gBLFnYn1ENCoAu8pZXEVAFF88CT1DSPAOnmcV47vBrvQlLpA1jg2Yp6iZb9RotAOGDJPrqgeDiqO xesYB09WPXEtWsqR5R5rvx-udouR9-w=@protonmail.ch>
2020-11-04 17:36 ` dxiri
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=CAMucfLxWUdzx5LfiYRhE+yypY8zC6ch868RO_NV231GCMvZo6Q@mail.gmail.com \
--to=dashohoxha@gmail.com \
--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).