Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: Sebastian Hyrvall <sh@keff.org>
Cc: "Janne Johansson" <icepic.dz@gmail.com>,
	"Daniel Gröber" <dxld@darkboxed.org>,
	"WireGuard mailing list" <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard address binding - how to fix?
Date: Tue, 21 May 2024 16:34:04 +0200	[thread overview]
Message-ID: <874jarfd43.fsf@ungleich.ch> (raw)
In-Reply-To: <f292656a-52c8-4258-8b6a-45064a702a8a@keff.org> (Sebastian Hyrvall's message of "Tue, 21 May 2024 21:11:31 +0700")


Hey Sebastian,


Sebastian Hyrvall <sh@keff.org> writes:
> [...]
> Anyway. I've waited for this binding option for years. It's insane to
> me it gets ignored.

I have to second this very strongly.

> One product is for example Mikrotik hardware. They don't want to
> implement third party patches so they are waiting for this bind-patch
> to be included in the kernel. Until then we're forced to use OpenVPN
> in our setups.

As well as this one. As written in the previous mail, virtually every
established networking software out there supports IP address binding,
with the exception of wireguard.

Dear wireguard authors, can be go into the direction of accepting an
already written patch (thanks again Daniel) or if that patch is not
suitable for some reason at least discuss what needs to be changed so
that IP address binding can make its way into wireguard?

BR,

Nico


-- 
Sustainable and modern Infrastructures by ungleich.ch

  reply	other threads:[~2024-05-21 14:41 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 [this message]
2024-05-26  3:59             ` d tbsky
2024-05-26  8:57               ` Nico Schottelius
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=874jarfd43.fsf@ungleich.ch \
    --to=nico.schottelius@ungleich.ch \
    --cc=dxld@darkboxed.org \
    --cc=icepic.dz@gmail.com \
    --cc=sh@keff.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 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).