From: John Huttley <john@mib-infotech.co.nz>
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard roaming behind a load balancer
Date: Thu, 17 Jan 2019 07:44:32 +1300 [thread overview]
Message-ID: <a6036478-50de-4b7e-01f8-a21c6f302876@mib-infotech.co.nz> (raw)
In-Reply-To: <CABbM=Lk6WQGctp7Z3YBYBcq9CKwRn-KWC-e8DeHxvYF+Cda8Og@mail.gmail.com>
If you are using an F5 LTM load balancer,
Set a keepalive timeout on wireguard.
Assign a UDP profile with a timeout greater than the wireguard keepalive
Assign the Profile to the UDP VIP
--John
On 16/01/2019 4:45 AM, pdub wrote:
> Greetings,
>
> WireGuard is a really cool project! Thanks!
>
> With WireGuard's native roaming support, I have a question about just
> how stateful/stateless the roaming is. Here's a hypothetical situation:
>
> Let's say WireGuard is being used to tunnel into a location and is
> served behind a load balancer for high availability. If both nodes have
> identical WireGuard config files at the start of WireGuard (and, for
> simplicity, let's assume the configurations don't change). If one node
> dies, the load balancer will automatically start sending packets to the
> standby node running WireGuard (perhaps existing on the same subnet as
> the other node, but with a different IP).
>
> In a sense, the server-side "peer" has just roamed from machine to
> another, but the public/Internet IP address didn't change (because that
> is assigned to the load balancer itself). Will this work with WireGuard
> today?
>
> TIA
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-01-16 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 16:45 WireGuard roaming behind a load balancer pdub
2019-01-16 18:44 ` John Huttley [this message]
2019-01-17 0:21 ` Ivan Labáth
2019-01-17 0:40 ` Samuel Holland
2019-01-17 11:54 ` Ivan Labáth
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=a6036478-50de-4b7e-01f8-a21c6f302876@mib-infotech.co.nz \
--to=john@mib-infotech.co.nz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.