From: Reid Rankin <firstname.lastname@example.org> To: Arvid Picciani <email@example.com> Cc: WireGuard mailing list <firstname.lastname@example.org> Subject: Re: separate allowedips from routing for multipath Date: Fri, 10 Dec 2021 18:29:59 -0500 [thread overview] Message-ID: <CAMaqUZ1yWooNbHdDhTAzrUeHtQCFn7QunSWdAdhdG+Ru6=K9Mg@mail.gmail.com> (raw) In-Reply-To: <CACD9L=CAinAO0CHRR25-sEoxCqNp_8BCqU9kJLK-Wztemail@example.com> 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.
next prev parent reply other threads:[~2021-12-10 23:30 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 [this message] 2021-12-11 7:28 ` Arvid Picciani
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='CAMaqUZ1yWooNbHdDhTAzrUeHtQCFn7QunSWdAdhdG+Ru6=K9Mg@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: separate allowedips from routing for multipath' \ /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
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).