Re: [ANNOUNCE] ipset 6.5 released

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 21 May 2011, Mr Dash Four wrote:

> gave up when I reached 16777216! ipset though was still insisting that the
> hash size is "full":
> 
> maxelem 15000 hashsize 4194304

When you asked about maxelem and hashsize, I wrote:

> > Is this a constraint coming from the "maxelem" value or the hash size? 
> > Could this be corrected by increasing either of these?

> Yes, of course: use larger maxelem. The initial hash size value can also 
> be increased, that way you can spare some internal resizings.

You still have "maxelem 15000". That means there can be at the maximum 
15000 element in the hash, and in another words, ipset regards the set 
full when its elem count reaches 15000.

Best regards,
Jozsef
-
E-mail  : kadlec@xxxxxxxxxxxxxxxxx, kadlec@xxxxxxxxxxxx
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
          H-1525 Budapest 114, POB. 49, Hungary
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux