From: SBlaze <dagent.geo@yahoo.com>
To: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>,
netfilter@lists.netfilter.org
Subject: Re: iptables analyzer - but slightly OT
Date: Tue, 28 Oct 2003 22:57:29 -0800 (PST) [thread overview]
Message-ID: <20031029065729.13556.qmail@web40203.mail.yahoo.com> (raw)
In-Reply-To: <3F9F5163.5020805@Loudoun-Fairfax.com>
You would have to have a complete dataset from every packet that
passesnetfilter to run any kind of rule analysis. Knowing which rule droppeda
packet isn't the same as knowing exactly which condition of that rulecaused the
drop. Could be iface, dport, sport, etc. You would almosthave to duplicate the
logic of netfilter itself to do any meaningfulanalysis at this level. However I
think a simpler but still useful toolcould be created by using the packet and
byte count kept by netfilterto sort rules within chains
Jeff
I agree with Jeff here. In fact I have been thinking about this for some time..
I even attempted something with bash script to do this...but my scripting
capability is not up to par..
Upon really thinking about it.... if I could just do a continuous iptables
-vxnL I would be happy. Perhaps some added counters for in which the the
differences are shown from the last time it is last checked... say like a 5-10
second delay?
Sort of a iptop heh.... an iptables in... top like display...
This is my dream!
SBlaze
=====
In the absence of order there will be chaos.
__________________________________
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
http://launch.yahoo.com/promos/britneyspears/
next prev parent reply other threads:[~2003-10-29 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 1:11 iptables analyzer Daniel Chemko
2003-10-29 5:34 ` Jeffrey Laramie
2003-10-29 6:57 ` SBlaze [this message]
2003-10-29 16:06 ` iptables analyzer - but slightly OT Jeffrey Laramie
2003-10-29 21:21 ` SBlaze
2003-10-30 1:20 ` Alistair Tonner
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=20031029065729.13556.qmail@web40203.mail.yahoo.com \
--to=dagent.geo@yahoo.com \
--cc=JALaramie@Loudoun-Fairfax.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