Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Pablo Sanchez" <pablo@blueoakdb.com>
To: 'Manish Jain' <manish.jain@globallogic.com>,
	netfilter@lists.netfilter.org
Subject: RE: maximum tuple support of hashlimit
Date: Tue, 31 Oct 2006 08:58:19 -0500	[thread overview]
Message-ID: <013301c6fcf4$9f019a60$0419a8c0@fly> (raw)
In-Reply-To: <002101c6fcd3$1ef3a1e0$6f00a8c0@synapse.com>

 

> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org 
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of 
> Manish Jain
> Sent: Tuesday, October 31, 2006 4:59 AM
> To: netfilter@lists.netfilter.org
> Subject: maximum tuple support of hashlimit
> 
> Hello Friends,
> 
> I am using hashlimit with hashlimit-mode as srcip-dstip. My 
> expectation is
> to have hashlimit for source-ip and destination ip tuple.
> 
> My question is, how many tuple, hashlimit can manage at any 
> instance of
> time?

Hi,

I'm not entirely sure about your question.  The 'man iptables' shows for
'hashlimit' the following two tunable parameters which may address your
question(?):

       --hashlimit-htable-size num
              The number of buckets of the hash table

       --hashlimit-htable-max num
              Maximum entries in the hash

Cheers,
---
Pablo Sanchez - Blueoak Database Engineering, Inc
Ph:    819.459.1926          Toll free:  888.459.1926
Cell:  819.918.9731                Pgr:  pablo_p@blueoakdb.com
Fax:   603.720.7723 (US)



  reply	other threads:[~2006-10-31 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22  1:05 installing ipsets Pollywog
2006-10-22 10:45 ` Martijn Lievaart
2006-10-31  9:58   ` maximum tuple support of hashlimit Manish Jain
2006-10-31 13:58     ` Pablo Sanchez [this message]
2006-11-07 11:53       ` Use of set-counters option of iptables Manish Jain

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='013301c6fcf4$9f019a60$0419a8c0@fly' \
    --to=pablo@blueoakdb.com \
    --cc=manish.jain@globallogic.com \
    --cc=netfilter@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox