From: Andreas Herz <andi@geekosphere.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter@vger.kernel.org
Subject: Re: [ANNOUNCE] ipset 6.13 released
Date: Tue, 10 Jul 2012 11:12:55 +0200 [thread overview]
Message-ID: <20120710091255.GP9358@workstation> (raw)
In-Reply-To: <alpine.DEB.2.00.1207011642300.2749@blackhole.kfki.hu>
On 01/07/12 at 16:44, Jozsef Kadlecsik wrote:
> On Sun, 1 Jul 2012, Andreas Herz wrote:
>
> > On 29/06/12 at 22:04, Jozsef Kadlecsik wrote:
> > > I have just released ipset 6.13 with a few bugfixes and some new features.
> >
> > Great, perfect timing, because i will go back to the testing and coding
> > stuff for my ipset setup :)
> >
> > > - Timeout fixing bug broke SET target special timeout value, fixed
> > > - Use MSEC_PER_SEC instead of harcoded value
> >
> > Does this also fix the jiffies issue with the kernel?
>
> That was fixed in the previous version.
>
I thought so, but:
> > But i will see it in my testcases nevertheless.
>
> I'm looking forward your testing results!
$IPSET create bset32 hash:ip family inet hashsize 1024 maxelem 65536
timeout 1000
ipset add bset32 192.168.0.21 timeout 2147483; ipset list
=> 192.168.0.21 timeout 2147482
ipset add bset32 192.168.0.20 timeout 2147485; ipset list
=> 192.168.0.20 timeout 1073650
although the range should be 0-4294967 as pointed when i enter a value
much higher.
This is for 32-Bit. But i still think this is caused by the kernel bug i
mentioned some time ago. Can you or anyone else confirm this issue with
32-Bit?
I have a workaround patch but i would love to get the maximum value to
lock IPs for more then ~12 days :)
--
Andreas Herz
prev parent reply other threads:[~2012-07-10 9:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 20:04 [ANNOUNCE] ipset 6.13 released Jozsef Kadlecsik
2012-07-01 10:46 ` Mr Dash Four
2012-07-01 12:09 ` Jozsef Kadlecsik
2012-07-01 12:19 ` Mr Dash Four
2012-07-01 12:37 ` Jozsef Kadlecsik
2012-07-01 12:44 ` Mr Dash Four
2012-07-01 12:52 ` Jozsef Kadlecsik
2012-07-01 13:17 ` Mr Dash Four
2012-07-01 15:21 ` Jozsef Kadlecsik
2012-07-01 16:52 ` Mr Dash Four
2012-07-01 21:30 ` Neal Murphy
2012-07-01 21:55 ` Jan Engelhardt
2012-07-01 22:59 ` Neal Murphy
2012-07-01 22:58 ` Amos Jeffries
2012-07-02 7:54 ` Jozsef Kadlecsik
2012-07-02 13:11 ` Mr Dash Four
2012-07-02 13:26 ` Jozsef Kadlecsik
2012-07-02 14:28 ` Mr Dash Four
2012-07-02 20:26 ` Jozsef Kadlecsik
2012-07-10 16:27 ` Alex Bligh
2012-07-01 18:32 ` Steven Kath
2012-07-01 13:21 ` Andreas Herz
2012-07-01 14:44 ` Jozsef Kadlecsik
2012-07-10 9:12 ` Andreas Herz [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=20120710091255.GP9358@workstation \
--to=andi@geekosphere.org \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter@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;
as well as URLs for NNTP newsgroup(s).