Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Athan <netfilter@miggy.org>
To: Javier Miguel =?unknown-8bit?Q?Rodr=EDguez?= <javier@talika.eii.us.es>
Cc: netfilter@lists.netfilter.org
Subject: Re: Rule matchup in iptables
Date: Thu, 6 Mar 2003 13:34:33 +0000	[thread overview]
Message-ID: <20030306133433.GE1025@miggy.org> (raw)
In-Reply-To: <20030306124758.GB23703@talika.eii.us.es>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

On Thu, Mar 06, 2003 at 01:47:58PM +0100, Javier Miguel Rodr?guez wrote:
> 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...

   iptables -nvL

The -v is the important bit here, you get 'packets' and 'bytes' counters
per rule then.  Adding -x will give exact byte numbers, rather than
summarising to K/M/G as the number grows.
  You can use -Z on a table to zero the counters when needed.

> 	Other question? How can I test iptables rules? In ipchains I
> could try them, but with iptables do I have to generate fake traffic?

  The only mention I can find of such in the man page is:

BUGS
       Check is not implemented (yet).

So I guess not.

-Ath
-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
                  Finger athan(at)fysh.org for PGP key
	   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2003-03-06 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 12:47 Rule matchup in iptables Javier Miguel =?unknown-8bit?q?Rodr=EDguez?=
2003-03-06 13:34 ` Athan [this message]
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=20030306133433.GE1025@miggy.org \
    --to=netfilter@miggy.org \
    --cc=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