From: Stephan von Krawczynski <skraw.ml@ithnet.com>
To: Adrian Larsen <alarsen@maidenheadbridge.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard address binding - how to fix?
Date: Mon, 24 Jun 2024 12:02:02 +0200 [thread overview]
Message-ID: <20240624120202.6fb011be@ithnet.com> (raw)
In-Reply-To: <43aac110-8699-41b3-bad8-7a38bf984b45@maidenheadbridge.com>
Thank you Adrian,
but remember, we are all trained professionals here mostly "skilled in the
art". Which means we all know _hacks_ to do just about everything.
But honestly, do you favor a security-based project where you have to hack
around its deficiencies to make it work how it should?
Btw, some of us aren't even allowed to post in the ML. Guess why ...
--
Regards,
Stephan
On Mon, 24 Jun 2024 10:36:06 +0100 Adrian Larsen
<alarsen@maidenheadbridge.com> wrote:
> Hi Friends,
>
> You can achieve address binding on a Linux box with a mix of marking, ip
> rules, ip route and Source NAT.
>
> 1) On WG interface, add "FwMark = 0x34" (the value 0x34 is an example,
> you can put any value here)
>
> 2) Create IP Rule "from all fwmark 0x34 lookup rt_wg0_out" -> this will
> force the outgoing packet to use the route table "rt_wg0_out"
>
> 3) On the route table "rt_wg0_out" create the default or specific route
> to force the packet market with 0x34 to leave using the interface where
> your desire "IP address" resides.
>
> 4) Create a POSTROUTING -> SNAT forcing mark 0x34 via the desired "IP
> address". This will bind your "IP address".
>
> Done! The packet with mark 0x34 will be routed via the correct interface
> using the source IP you want.
>
> I hope this helps.
>
> Best regards,
>
> Adrian Larsen
> Maidenhead Bridge
> Cloud Security Connectors for SSE vendors.
> m: +44 7487640352
> e:alarsen@maidenheadbridge.com
>
> On 09/06/2024 16:39, Nico Schottelius wrote:
> > 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
> >>
>
next prev parent reply other threads:[~2024-11-18 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2024-06-27 11:33 ` Nico Schottelius
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: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
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=20240624120202.6fb011be@ithnet.com \
--to=skraw.ml@ithnet.com \
--cc=alarsen@maidenheadbridge.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).