From: Duncan Roe <duncan_roe@optusnet.com.au>
To: netfilter-devel@vger.kernel.org
Subject: And another thing
Date: Thu, 4 Jan 2018 09:59:29 +1100 [thread overview]
Message-ID: <20180103225929.GC3302@dimstar.local.net> (raw)
In-Reply-To: <20180103222640.GB3302@dimstar.local.net>
On Thu, Jan 04, 2018 at 09:26:40AM +1100, Duncan Roe wrote:
> On Wed, Jan 03, 2018 at 03:41:08PM +0100, Pablo Neira Ayuso wrote:
> > iptables-translate -A INPUT -m tcp -p tcp --dport 80 -m hashlimit --hashlimit-above 200kb/s --hashlimit-burst 1mb --hashlimit-mode srcip,dstport --hashlimit-name http2 --hashlimit-htable-expire 3000 -j DROP
> >
> > shows:
> >
> > nft add rule ip filter INPUT tcp dport 80 flow table http2 { tcp dport . ip saddr timeout 3s limit rate over 200 kbytes/second burst 1 mbytes burst 6 packets} counter drop
> >
> > which prints burst twice, this is not correct.
> >
> > Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> > ---
Not actually related to the patch, but I happened to notice:
> 769 if (info->cfg.mode & XT_HASHLIMIT_BYTES) {
> 770 uint32_t burst = 0;
> 771 if (cb->xflags & F_BURST) {
> 772 if (info->cfg.burst < cost_to_bytes(info->cfg.avg))
> 773 xtables_error(PARAMETER_PROBLEM,
> 774 "burst cannot be smaller than %lub", cost_to_bytes(info->cfg.avg));
> 775
> 776 burst = info->cfg.burst;
> 777 burst /= cost_to_bytes(info->cfg.avg);
> 778 if (info->cfg.burst % cost_to_bytes(info->cfg.avg))
> 779 burst++;
> 780 if (!(cb->xflags & F_HTABLE_EXPIRE))
> 781 info->cfg.expire = XT_HASHLIMIT_BYTE_EXPIRE_BURST * 1000;
> 782 }
> 783 info->cfg.burst = burst;
> 784 } else if (info->cfg.burst > XT_HASHLIMIT_BURST_MAX)
> 785 burst_error();
What is that final "else" claues there for? No hashlimit was specified so why
check its value?
Cheers ... Duncan.
next prev parent reply other threads:[~2018-01-03 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 14:41 [PATCH iptables] extensions: hashlimit: fix incorrect burst in translations Pablo Neira Ayuso
2018-01-03 22:26 ` Duncan Roe
2018-01-03 22:59 ` Duncan Roe [this message]
2018-01-04 9:53 ` Pablo Neira Ayuso
2018-01-04 10:56 ` Duncan Roe
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=20180103225929.GC3302@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.