From: Florian Westphal <fw@strlen.de>
To: Cole Dishington <Cole.Dishington@alliedtelesis.co.nz>
Cc: pablo@netfilter.org, kadlec@netfilter.org, fw@strlen.de,
davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, netdev@vger.kernel.org,
Anthony Lineham <anthony.lineham@alliedtelesis.co.nz>,
Scott Parlane <scott.parlane@alliedtelesis.co.nz>,
Blair Steven <blair.steven@alliedtelesis.co.nz>
Subject: Re: [PATCH net v4] net: netfilter: Fix port selection of FTP for NF_NAT_RANGE_PROTO_SPECIFIED
Date: Thu, 16 Sep 2021 13:26:41 +0200 [thread overview]
Message-ID: <20210916112641.GC20414@breakpoint.cc> (raw)
In-Reply-To: <20210916041057.459-1-Cole.Dishington@alliedtelesis.co.nz>
Cole Dishington <Cole.Dishington@alliedtelesis.co.nz> wrote:
> + /* Avoid applying nat->range to the reply direction */
> + if (!exp->dir || !nat->range_info.min_proto.all || !nat->range_info.max_proto.all) {
> + min = ntohs(exp->saved_proto.tcp.port);
> + range_size = 65535 - min + 1;
> + } else {
> + min = ntohs(nat->range_info.min_proto.all);
> + range_size = ntohs(nat->range_info.max_proto.all) - min + 1;
> + }
> +
> /* Try to get same port: if not, try to change it. */
> - for (port = ntohs(exp->saved_proto.tcp.port); port != 0; port++) {
> - int ret;
> + first_port = ntohs(exp->saved_proto.tcp.port);
> + if (min > first_port || first_port > (min + range_size - 1))
> + first_port = min;
>
> + for (i = 0, port = first_port; i < range_size; i++, port = (port - first_port + i) % range_size) {
This looks complicated. As far as I understand, this could instead be
written like this (not even compile tested):
/* Avoid applying nat->range to the reply direction */
if (!exp->dir || !nat->range_info.min_proto.all || !nat->range_info.max_proto.all) {
min = 1;
max = 65535;
range_size = 65535;
} else {
min = ntohs(nat->range_info.min_proto.all);
max = ntohs(nat->range_info.max_proto.all);
range_size = max - min + 1;
}
/* Try to get same port: if not, try to change it. */
port = ntohs(exp->saved_proto.tcp.port);
if (port < min || port > max)
port = min;
for (i = 0; i < range_size; i++) {
exp->tuple.dst.u.tcp.port = htons(port);
ret = nf_ct_expect_related(exp, 0);
if (ret != -EBUSY)
break;
port++;
if (port > max)
port = min;
}
if (ret != 0) {
...
AFAICS this is the same, we loop at most range_size times,
in case range_size is 64k, we will loop through all (hmmm,
not good actually, but better make that a different change)
else through given min - max range.
If orig port was in-range, we try it first, then increment.
If port exceeds upper bound, cycle back to min.
What do you think?
next prev parent reply other threads:[~2021-09-16 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 4:10 [PATCH net v4] net: netfilter: Fix port selection of FTP for NF_NAT_RANGE_PROTO_SPECIFIED Cole Dishington
2021-09-16 11:26 ` Florian Westphal [this message]
2021-09-16 20:30 ` Cole Dishington
2021-09-17 14:04 ` Florian Westphal
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=20210916112641.GC20414@breakpoint.cc \
--to=fw@strlen.de \
--cc=Cole.Dishington@alliedtelesis.co.nz \
--cc=anthony.lineham@alliedtelesis.co.nz \
--cc=blair.steven@alliedtelesis.co.nz \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=scott.parlane@alliedtelesis.co.nz \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).