From: Javier Miguel =?unknown-8bit?q?Rodr=EDguez?= <javier@talika.eii.us.es>
To: netfilter@lists.netfilter.org
Subject: Rule matchup in iptables
Date: Thu, 6 Mar 2003 13:47:58 +0100 [thread overview]
Message-ID: <20030306124758.GB23703@talika.eii.us.es> (raw)
Hello
I have a iptables based firewall, with 5 gigabit ethernet
adapters and almost 8000 rules (ouch!). This is a "test bed", (still) not a
production enviroment
I can see delays in traffic when crosses the firewall
(miliseconds). I want to optimize the firewall rules (we use a LOT of
VoIP) , so this is my question: Is there any way to know when a packet matches a rule?
-j LOG is not feasible (thousands of packets per second). I want something like this:
Last two hours:
Rule 1: 15000 hits, 150 megabytes
Rule 2: 3500 hits, 34 megabytes
Rule 3: 9675 hits, 2 megabytes
ad infinitum...
Other question? How can I test iptables rules? In ipchains I
could try them, but with iptables do I have to generate fake traffic?
Thank you for your support.
next reply other threads:[~2003-03-06 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 12:47 Javier Miguel =?unknown-8bit?q?Rodr=EDguez?= [this message]
2003-03-06 13:34 ` Rule matchup in iptables Athan
2003-03-06 21:08 ` ...
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=20030306124758.GB23703@talika.eii.us.es \
--to=javier@talika.eii.us.es \
--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