From: Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>
To: netfilter@lists.netfilter.org
Subject: Re: iptables analyzer - but slightly OT
Date: Wed, 29 Oct 2003 11:06:32 -0500 [thread overview]
Message-ID: <3F9FE588.5090409@Loudoun-Fairfax.com> (raw)
In-Reply-To: <20031029065729.13556.qmail@web40203.mail.yahoo.com>
SBlaze wrote:
>
>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...
>
>
I think this is a very cool idea that should be much easier to implement
than any kind of rule analyzer. Even better, you could calculate the
delta between -vxnL readings and drop it into a graph that updates at
user defined intervals, kinda like the bar graph model used in spectrum
analyzers. You could "see" traffic on each rule in real time and know
instantly if a particular rule was getting pounded. Maybe set "alarm"
limits based on % of historical traffic or a user defined level. Set a
longer (daily) interval and it would produce the kind of output Chris
Brenton could use with a bar for each of his reject rules. Perhaps an
option to normalize average traffic to a straight line so that abnormal
traffic would look like "static" with positive and negative deflection
from the x-axis. Ooohhh, my head is spinning . . .
Jeff
next prev parent reply other threads:[~2003-10-29 16:06 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 ` iptables analyzer - but slightly OT SBlaze
2003-10-29 16:06 ` Jeffrey Laramie [this message]
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=3F9FE588.5090409@Loudoun-Fairfax.com \
--to=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