From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: "Daniel Gröber" <dxld@darkboxed.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: Wireguard address binding - how to fix?
Date: Tue, 21 May 2024 09:21:11 +0200 [thread overview]
Message-ID: <87msojhbq0.fsf@ungleich.ch> (raw)
In-Reply-To: <20240514113648.neaj6kfazx4fi7af@House.clients.dxld.at> ("Daniel Gröber"'s message of "Tue, 14 May 2024 13:36:48 +0200")
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Hello Jason,
do you mind applying the patch from Daniel? Or is there anything wrong with it?
Daniel: amazing work, I was not aware that you have already put in the
hard work, thank you so very much!
The world (*) is suffering because of the lack of IP address binding in wireguard.
Best regards,
Nico
(*) With world I refer to every engineer that needs to run wireguard in
non-trivial situations with multiple IP addresses on one host, which is
extremely common for anything that routes.
Daniel Gröber <dxld@darkboxed.org> writes:
> On Tue, May 14, 2024 at 12:50:25PM +0200, Nico Schottelius wrote:
>> To the wireguard authors: what needs to be done to add IP address
>> binding so that packets are always sent from a specific IP address?
>
> Implemented, but wating for Jason to respond:
> https://lore.kernel.org/netdev/20240219114334.3057169-1-dxld@darkboxed.org/T/
>
> --Daniel
[-- Attachment #2.1: Type: text/plain, Size: 62 bytes --]
--
Sustainable and modern Infrastructures by ungleich.ch
[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2024-05-21 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 10:50 Wireguard address binding - how to fix? Nico Schottelius
2024-05-14 11:36 ` Daniel Gröber
2024-05-21 7:21 ` Nico Schottelius [this message]
2024-05-21 11:11 ` Janne Johansson
2024-05-21 12:55 ` Stephan von Krawczynski
2024-05-21 12:58 ` Nico Schottelius
2024-05-21 14:11 ` Sebastian Hyrvall
2024-05-21 14:34 ` Nico Schottelius
2024-05-26 3:59 ` d tbsky
2024-05-26 8:57 ` Nico Schottelius
2024-06-09 15:39 ` Nico Schottelius
2024-05-22 8:53 ` Stephan von Krawczynski
[not found] <740ee793-0ed2-4cf6-ba4a-07268b46b761@maidenheadbridge.com>
2024-06-24 9:36 ` Fwd: " Adrian Larsen
2024-06-24 10:02 ` Stephan von Krawczynski
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=87msojhbq0.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=Jason@zx2c4.com \
--cc=dxld@darkboxed.org \
--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.