From: Duncan Roe <duncan_roe@optusnet.com.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harsha Sharma <harshasharmaiitr@gmail.com>,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v2] extensions: libxt_hashlimit: Do not print default timeout and burst
Date: Sun, 31 Dec 2017 09:51:10 +1100 [thread overview]
Message-ID: <20171230225110.GA10178@dimstar.local.net> (raw)
In-Reply-To: <20171228105236.hmii7xbk5jtctmpr@salvia>
On Thu, Dec 28, 2017 at 11:52:36AM +0100, Pablo Neira Ayuso wrote:
> Cc'ing Duncan.
No need - I'm on netfilter-devel ;)
>
> On Thu, Dec 28, 2017 at 12:58:33PM +0530, Harsha Sharma wrote:
> > Do not print timeout and burst in case default values are used.
> > For e.g.
> > iptables-translate -A INPUT -m tcp -p tcp --dport 80 -m hashlimit
> > --hashlimit-above 200/sec --hashlimit-mode srcip,dstport
> > --hashlimit-name http1 -j DROP
> >
> > nft add rule ip filter INPUT tcp dport 80 flow table http1 { tcp dport .
> > ip saddr limit rate over 200/second } counter drop
>
> This is what I was asking for.
>
> Applied, thanks Harsha.
>
> @Duncan: I think you can update the wiki again after this, given that
> now those values should not be printed.
I tested after applying the patch and now the second example is broken:
> 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
> 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
The traling "burst 6 packets" should not be there.
I propose to leave the wiki until this is fixed.
Cheers ... Duncan.
next prev parent reply other threads:[~2017-12-30 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 7:28 [PATCH v2] extensions: libxt_hashlimit: Do not print default timeout and burst Harsha Sharma
2017-12-28 10:52 ` Pablo Neira Ayuso
2017-12-30 22:51 ` Duncan Roe [this message]
2017-12-30 23:16 ` Pablo Neira Ayuso
2018-01-02 22:47 ` Duncan Roe
2018-01-03 13:53 ` Pablo Neira Ayuso
2018-01-15 1:45 ` Duncan Roe
2018-01-16 1:23 ` Pablo Neira Ayuso
[not found] ` <20180116011537.b4xm2mxlabn5tsfl@salvia>
[not found] ` <20180116124143.5s6exg3467ozmobb@salvia>
[not found] ` <20180116204554.GA27044@dimstar.local.net>
[not found] ` <20180116215217.GA27232@dimstar.local.net>
[not found] ` <20180116223930.ftuagn4vtkvd2nka@salvia>
[not found] ` <20180119014815.GA4882@dimstar.local.net>
[not found] ` <20180119022722.duu5l3esazkox43z@salvia>
[not found] ` <20180119022757.z5ir6zcytaabqntc@salvia>
2018-01-20 6:11 ` Duncan Roe
2018-01-20 9:21 ` Pablo Neira Ayuso
2018-01-20 12:47 ` Pablo Neira Ayuso
2018-01-20 13:35 ` Duncan Roe
2018-01-20 13:42 ` 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=20171230225110.GA10178@dimstar.local.net \
--to=duncan_roe@optusnet.com.au \
--cc=harshasharmaiitr@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.