From: Antonio Quartulli <a@unstable.cc>
To: Nico Schottelius <nico.schottelius@ungleich.ch>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard broken with ip rule due to missing address binding
Date: Wed, 19 Jun 2024 12:01:07 +0200 [thread overview]
Message-ID: <9e91adb2-b155-4eef-8604-a2f762a98d4d@unstable.cc> (raw)
In-Reply-To: <87h6dpi7zp.fsf@ungleich.ch>
Hi,
On 19/06/2024 11:42, Nico Schottelius wrote:
> I really hope the address binding issue can be solved soon, especially
> giving there is already a patch for it available.
Question: instead of implementing pure IP binding, may it help to
implement some logic so that messages to a peer are always sent using
the IP where previous packets were received?
Cheers,
--
Antonio Quartulli
next prev parent reply other threads:[~2024-06-19 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 9:42 Nico Schottelius
2024-06-19 10:01 ` Antonio Quartulli [this message]
2024-06-19 10:12 ` Nico Schottelius
2024-06-19 10:19 ` Antonio Quartulli
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=9e91adb2-b155-4eef-8604-a2f762a98d4d@unstable.cc \
--to=a@unstable.cc \
--cc=nico.schottelius@ungleich.ch \
--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).