From: Florian Westphal <fw@strlen.de>
To: Jeremy Sowden <jeremy@azazel.net>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nf-next v3 0/4] Support for shifted port-ranges in NAT
Date: Fri, 24 Mar 2023 23:36:46 +0100 [thread overview]
Message-ID: <20230324223646.GA17250@breakpoint.cc> (raw)
In-Reply-To: <20230324190419.543888-1-jeremy@azazel.net>
Jeremy Sowden <jeremy@azazel.net> wrote:
> Commit 2eb0f624b709 ("netfilter: add NAT support for shifted portmap
> ranges") introduced support for shifting port-ranges in DNAT. This
> allows one to redirect packets intended for one port to another in a
> range in such a way that the new port chosen has the same offset in the
> range as the original port had from a specified base value.
>
> For example, by using the base value 2000, one could redirect packets
> intended for 10.0.0.1:2000-3000 to 10.10.0.1:12000-13000 so that the old
> and new ports were at the same offset in their respective ranges, i.e.:
>
> 10.0.0.1:2345 -> 10.10.0.1:12345
>
> However, while support for this was added to the common DNAT infra-
> structure, only the xt_nat module was updated to make use of it. This
> patch-set extends the core support and updates all the nft NAT modules
> to support it too.
>
> Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970672
> Link: https://bugzilla.netfilter.org/show_bug.cgi?id=1501
I have no objections to the kernel side.
Pablo, unless you disagree I'm inclined to merge this.
prev parent reply other threads:[~2023-03-24 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 19:04 [PATCH nf-next v3 0/4] Support for shifted port-ranges in NAT Jeremy Sowden
2023-03-24 19:04 ` [PATCH nf-next v3 1/4] netfilter: nat: extend core support for shifted port-ranges Jeremy Sowden
2023-03-24 19:04 ` [PATCH nf-next v3 2/4] netfilter: nft_nat: add " Jeremy Sowden
2023-03-24 19:04 ` [PATCH nf-next v3 3/4] netfilter: nft_masq: " Jeremy Sowden
2023-03-24 19:04 ` [PATCH nf-next v3 4/4] netfilter: nft_redir: " Jeremy Sowden
2023-03-24 22:36 ` Florian Westphal [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=20230324223646.GA17250@breakpoint.cc \
--to=fw@strlen.de \
--cc=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
/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