From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: d tbsky <tbskyd@gmail.com>, Jason A. Donenfeld <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard address binding - how to fix?
Date: Sun, 26 May 2024 10:57:52 +0200 [thread overview]
Message-ID: <87bk4tc5m7.fsf@ungleich.ch> (raw)
In-Reply-To: <CAC6SzHJFRNPsLNSd7_w8qQwtyfHLvZtf5SeTS-gvAcY_wAidXQ@mail.gmail.com> (d. tbsky's message of "Sun, 26 May 2024 11:59:50 +0800")
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
d tbsky <tbskyd@gmail.com> writes:
> I remembered how exciting when I tested wireguard at 2017. until I
> asked muti-home question in the list.
> wiregurad is beautiful,elegant,fast but not easy to get along with.
> openvpn is not so amazing but it can get the job done.
Nice summary, hits the nail quite well.
Jason, do you mind having a look at the submitted patches for IP address
binding and comment on them? Or alternatively can you give green light
for generally moving forward so that a direct inclusion in the Linux
kernel would be accepted?
Best regards,
Nico
[-- 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-26 9:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 10:50 Nico Schottelius
2024-05-14 11:36 ` Daniel Gröber
2024-05-21 7:21 ` Nico Schottelius
2024-05-21 11:11 ` Janne Johansson
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 [this message]
2024-06-09 15:39 ` Nico Schottelius
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=87bk4tc5m7.fsf@ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=Jason@zx2c4.com \
--cc=tbskyd@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).