All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Peter <pme@ufh.se>
Cc: 이근수 <kslee109@gmail.com>, netfilter-devel@lists.netfilter.org
Subject: Re: How many rules were supported iptables?
Date: Fri, 20 Oct 2006 09:06:42 +0200	[thread overview]
Message-ID: <45387582.5050901@cosmosbay.com> (raw)
In-Reply-To: <45387015.40305@ufh.se>

Peter a écrit :
> 이근수 wrote:
> 
>> Hi All.
>> I have a problem that is how many rules were supported iptables.
>> The program which I maintain and repair generated iptables rules 
>> automatically.
>> Now, I encounter this problem.
>> Source and destination IP address is written range by user.( ex, 
>> 1.1.1.1~1.1.1.10 ) then our program generated 10 IP address(1.1.1.1, 
>> 1.1.1.2, 1.1.1.3, … , 1.1.1.10) and make 10 iptables rules.
>> Unfortunately, user wrote iptables rules like this, 10,000 rules is 
>> generated.
>>  “ iptalbes –A FORWARD –p tcp –s 1.1.1.1~1.1.1.100 –d 
>> 2.2.2.1~2.2.2.100 –j QUEUE”.
>> Do 10,000 rules operate safely?? Or Some rules don’t operate normally??
>> If some rules don’t operate normally, how many rules iptables does 
>> support??
>>
>>
>>  
>>
> It's the 4 MB in total size of rules. (This is the maximum size of a 
> chunc of data copy from userspace to kernel space in
> one syscall)
Hi Peter

I was not aware on this 4MB limit.
Could you please tell us where this limit is applied in kernel sources ?

Thank you

  reply	other threads:[~2006-10-20  7:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  6:28 How many rules were supported iptables? 이근수
2006-10-20  6:43 ` Peter
2006-10-20  7:06   ` Eric Dumazet [this message]
2006-10-26 12:12   ` Jesper Dangaard Brouer
2006-10-26 15:29     ` Paul C Diem
2006-10-20  7:13 ` m.innocenti
  -- strict thread matches above, loose matches on Subject: below --
2006-10-26 12:39 scott comer (sccomer)
2006-10-20  6:18 이근수
2006-10-20  6:47 ` Maik Hentsche
2006-08-29  9:47 "이근수"

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=45387582.5050901@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=kslee109@gmail.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pme@ufh.se \
    /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.