Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Ashish SHUKLA <ashish.is@lostca.se>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Force a specific IP for outgoing WG traffic with SNAT?
Date: Sat, 18 Mar 2023 00:54:51 +0500	[thread overview]
Message-ID: <20230318005451.7212e6c9@nvm> (raw)
In-Reply-To: <e4f7dc477cd14e14a75e304878e6cb05@lostca.se>

On Sat, 18 Mar 2023 01:13:53 +0530
Ashish SHUKLA <ashish.is@lostca.se> wrote:

> 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 
> genkey. Required.
> 
>             •      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.

I was not aware there was such an option. For now the task described in the
original message is no longer required, I will try fwmark next time when it
might be. Thanks!

-- 
With respect,
Roman

      reply	other threads:[~2023-03-17 19:57 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
2023-03-17 19:54   ` Roman Mamedov [this message]

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=20230318005451.7212e6c9@nvm \
    --to=rm@romanrm.net \
    --cc=ashish.is@lostca.se \
    --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).