From: Svenne Krap <svenne@kracon.dk>
To: wireguard@lists.zx2c4.com
Subject: Re: Source IP for multihomed peer
Date: Fri, 15 Oct 2021 10:54:59 +0200 [thread overview]
Message-ID: <5ec4906f-db2b-363a-db38-ac7179af83b5@kracon.dk> (raw)
In-Reply-To: <87wnmfj9kq.fsf@proton.d.airelinux.org>
On 15.10.2021 04.39, Benda Xu wrote:
> We have met exactly the same problem.
Have you tried SNAT from iptables? Is that a viable work-around?
Svenne
next prev parent reply other threads:[~2021-10-15 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 8:30 Svenne Krap
2021-10-15 2:39 ` Benda Xu
2021-10-15 7:57 ` Chriztoffer Hansen
2021-10-15 8:25 ` Benda Xu
2021-10-15 8:54 ` Svenne Krap [this message]
2021-10-15 10:14 ` Toke Høiland-Jørgensen
2021-10-15 11:14 ` Chriztoffer Hansen
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=5ec4906f-db2b-363a-db38-ac7179af83b5@kracon.dk \
--to=svenne@kracon.dk \
--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).