From: Ashish SHUKLA <firstname.lastname@example.org>
To: Roman Mamedov <email@example.com>
Subject: Re: Force a specific IP for outgoing WG traffic with SNAT?
Date: Sat, 18 Mar 2023 01:13:53 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 2023-02-17 00:37, Roman Mamedov wrote:
> I'm trying to move all my WG communication with peers to a non-primary
> IP of my server.
> It has IPs added like this:
> inet6 2001:db8::ca6c/128 scope global deprecated
> valid_lft forever preferred_lft 0sec
> inet6 2001:db8::1/128 scope global nodad
> valid_lft forever preferred_lft forever
> What I tried:
> ip6tables -t nat -I POSTROUTING -d 2000::/3 -p udp --dport 51820 -j
> SNAT --to-source 2001:db8::ca6c
> Also tried to filter by --sport, and also briefly without a port filter
> at all.
> This has zero effect, as shown by tcpdump all the WG traffic still
> originates from 2001:db8::1
> Does anyone have an idea why is that? Thanks
Did you try filtering based on fwmark ?
CONFIGURATION FILE FORMAT
The configuration file format is based on INI. There are two
top level sections -- Interface and Peer. Multiple Peer sections may be
specified, but only one Interface section may be specified.
The Interface section may contain the following fields:
• PrivateKey — a base64 private key generated by wg
• ListenPort — a 16-bit port for listening. Optional; if
not specified, chosen randomly.
• FwMark — a 32-bit fwmark for outgoing packets. If set
to 0 or "off", this option is disabled. May be specified in hexadecimal
by prepending "0x". Optional.
"It could be that the purpose of your life is only to serve as a warning
to others." (Ashleigh Brilliant)
next prev parent reply other threads:[~2023-03-17 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 19:07 Roman Mamedov
2023-03-17 19:43 ` Ashish SHUKLA [this message]
2023-03-17 19:54 ` Roman Mamedov
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).