All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: d tbsky <tbskyd@gmail.com>
Cc: Jason A. Donenfeld <Jason@zx2c4.com>,
	 WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard address binding - how to fix?
Date: Sun, 09 Jun 2024 17:39:46 +0200	[thread overview]
Message-ID: <87tti2xgzh.fsf@ungleich.ch> (raw)
In-Reply-To: <87bk4tc5m7.fsf@ungleich.ch> (Nico Schottelius's message of "Sun,  26 May 2024 10:57:52 +0200")

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]


Jason,

may I shortly ask what your opinion is on the patch and whether there is
a way forward to make wireguard usable on systems with multiple IP
addresses?

Best regards,

Nico

Nico Schottelius <nico.schottelius@ungleich.ch> writes:

> 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 --]

  reply	other threads:[~2024-06-09 15:40 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
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 [this message]
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=87tti2xgzh.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 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.