From: Chriztoffer Hansen <ch@ntrv.dk>
To: Benda Xu <heroxbd@gentoo.org>
Cc: Svenne Krap <svenne@kracon.dk>,
"WireGuard List (wireguard@lists.zx2c4.com)"
<wireguard@lists.zx2c4.com>
Subject: Re: Source IP for multihomed peer
Date: Fri, 15 Oct 2021 09:57:20 +0200 [thread overview]
Message-ID: <CA+cYV6t=doigei7mH-77oZrq=_uMmCn_kRxhfXku+XC75moU=A@mail.gmail.com> (raw)
In-Reply-To: <87wnmfj9kq.fsf@proton.d.airelinux.org>
On Fri, 15 Oct 2021 at 04:39, Benda Xu <heroxbd@gentoo.org> wrote:
> > From the documentation Listenport only seems like the portnumber and
> > there seems to be no way to set the source ip.
>
> It has been discussed on the list several times. But Jason seems not
> convinced of the necessity of address binding.
>
> https://lists.zx2c4.com/pipermail/wireguard/2017-May/001280.html
> https://lists.zx2c4.com/pipermail/wireguard/2019-March/003938.html
> https://lists.zx2c4.com/pipermail/wireguard/2018-June/003013.html
> https://lists.zx2c4.com/pipermail/wireguard/2017-November/002017.html
>
> Rulin and I tried to implement an address binding feature at,
>
> https://github.com/FireflyTang/linux-wireguard-bind
>
> It was verified to work with Linux-5.7.
In the prototyping patch you developed for WireGuard, did you consider
prototyping being able to bind to an interface, instead of explicitly
specifying an IP address? An example case for being able to bind to an
interface could be a multi-wan connected firewall/router with dynamic
public IP addresses offered by the upstream provider no at least one
connection. E.g. Primary fiber line, backup DSL line.
/Chriztoffer
next prev parent reply other threads:[~2021-10-15 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 8:30 Svenne Krap
2021-10-15 2:39 ` Benda Xu
2021-10-15 7:57 ` Chriztoffer Hansen [this message]
2021-10-15 8:25 ` Benda Xu
2021-10-15 8:54 ` Svenne Krap
2021-10-15 10:14 ` Toke Høiland-Jørgensen
2021-10-15 11:14 ` Chriztoffer Hansen
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='CA+cYV6t=doigei7mH-77oZrq=_uMmCn_kRxhfXku+XC75moU=A@mail.gmail.com' \
--to=ch@ntrv.dk \
--cc=heroxbd@gentoo.org \
--cc=svenne@kracon.dk \
--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).