Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Daniel Gröber" <dxld@darkboxed.org>
To: Daniel <tech@tootai.net>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: Endpoint failover ip
Date: Tue, 1 Aug 2023 11:07:07 +0200	[thread overview]
Message-ID: <20230801090707.lrsxcpwjkrwftarc@House.clients.dxld.at> (raw)
In-Reply-To: <b112c414-36c6-d87f-3568-f3a740c52877@tootai.net>

On Tue, Aug 01, 2023 at 10:33:03AM +0200, Daniel wrote:
> > On Mon, Jul 31, 2023 at 11:39:35PM +0200, Daniel wrote:
> > > I create a hostname with few IPs v4 & v6 for my wireguard server. I faced
> > > today a problem that after a failure with the ip a customer wg was
> > > registered, it continue to try to register with this ip insteed to fallback
> > > to another one.
> > [...]
> > [1]: Supporting multiple active endpoints is where we have to head to fix
> > this properly IMO, see my recent proposal
> > https://lists.zx2c4.com/pipermail/wireguard/2023-July/008111.html
> 
> Yes, that's exactly the problem. Will see with babeld but hope that
> something native can be done in wireguard.

I'm on the babel-users ML (babel-users@alioth-lists.debian.net) if it gives
you any trouble. Getting the filtering setup just right for the VPN
use-case can be a bit daunting if you've never used a routing daemon
before.

    https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/babel-users

--Daniel


      reply	other threads:[~2023-08-01  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 21:39 Daniel
2023-07-31 22:27 ` Daniel Gröber
2023-08-01  8:33   ` Daniel
2023-08-01  9:07     ` Daniel Gröber [this message]

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=20230801090707.lrsxcpwjkrwftarc@House.clients.dxld.at \
    --to=dxld@darkboxed.org \
    --cc=tech@tootai.net \
    --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).