From: Arvid Picciani <aep@exys.org>
To: Reid Rankin <reidrankin@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: separate allowedips from routing for multipath
Date: Sat, 11 Dec 2021 08:28:37 +0100 [thread overview]
Message-ID: <CACD9L=BWM_OPmBjTh7JUsBkL3A6V_hiyHDos=1MrEkJ5P3QhWg@mail.gmail.com> (raw)
In-Reply-To: <CAMaqUZ1yWooNbHdDhTAzrUeHtQCFn7QunSWdAdhdG+Ru6=K9Mg@mail.gmail.com>
Thanks Reid,
i'm aware of how that works, but that's not the question.
V is an IP routed on A1 or A2, not a "road warrior" case.
I can look into if port reuse is possible if a patchset doing that
would be acceptable.
On Sat, Dec 11, 2021 at 12:30 AM Reid Rankin <reidrankin@gmail.com> wrote:
>
> WireGuard doesn't care what address V has, because peers are defined
> by their public key. If V switches from A1 to A2, upon receiving a
> handshake packet from V's key from the address A2, B will start
> sending packets for V out to A2. Incoming packets can arrive from any
> IP; if they're from a connection with V, V's AllowedIP rules will be
> applied.
--
+4916093821054
prev parent reply other threads:[~2021-12-11 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 15:36 Arvid Picciani
2021-12-10 23:29 ` Reid Rankin
2021-12-11 7:28 ` Arvid Picciani [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='CACD9L=BWM_OPmBjTh7JUsBkL3A6V_hiyHDos=1MrEkJ5P3QhWg@mail.gmail.com' \
--to=aep@exys.org \
--cc=reidrankin@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).