From: Alistair Tonner <Alistair@nerdnet.ca>
To: SBlaze <dagent.geo@yahoo.com>,
Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com>,
netfilter@lists.netfilter.org
Subject: Re: iptables analyzer - but slightly OT
Date: Wed, 29 Oct 2003 20:20:08 -0500 [thread overview]
Message-ID: <200310292020.08103.Alistair@nerdnet.ca> (raw)
In-Reply-To: <20031029212129.58201.qmail@web40207.mail.yahoo.com>
On October 29, 2003 04:21 pm, SBlaze wrote:
> --- Jeffrey Laramie <JALaramie@Loudoun-Fairfax.com> wrote:
> > 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
If you throw a -Z in there you clear the counters in iptables.
you could accumulate the counters internally and map the differences.
... You would have to do some fancy stuff with
iptables-save/awk/sed/iptables-restore afterwards to put the counters back
though.
> >
> > >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
>
> Again I concur with ya Jeff. The options I suggested would be great
> building blocks for...further statistical and analytical advacnment of the
> iptables/netfilter firewall. Let's face it, us geeks like numbers. I'm
> amazed that this has never come up before or hasn't already become a part
> of iptables. We want real time data... and be able to shape it however we
> want..be it console display, SQL databases, or any other means. We like
> options and access to data even if we don't use those options.
>
> However what we like and what we can get are sometimes very different. We
> have all these really great ideas. Getting developers to acknoledge that
> this is a nice feature and perhaps would be invalueable to some is not
> always easy. I believe you said you don't program Jeff and neither do I. It
> may be difficult to get deverlopers to take note of this..since they may
> not consider it "vital" to the iptables core.
>
> I will be the first to admit I really want this. I just hope what I want is
> shared throughout the community so that in versions soon... iptables will
> have easier ways to analyze what it does. Jeff and I think the simplest
> point is -vxL...anyone else out there post up on this. If we get enough
> support we can go about communicating to the developers a growing need.
> Otherwise Jeff and I just might be on our own.
>
> God Bless the OS Community and the makers of iptables/netfilter
> SBlaze
>
>
>
>
> =====
> In the absence of order there will be chaos.
>
> __________________________________
> Do you Yahoo!?
> Exclusive Video Premiere - Britney Spears
> http://launch.yahoo.com/promos/britneyspears/
--
Alistair Tonner
nerdnet.ca
Senior Systems Analyst - RSS
Any sufficiently advanced technology will have the appearance of magic.
Lets get magical!
prev parent reply other threads:[~2003-10-30 1:20 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
2003-10-29 21:21 ` SBlaze
2003-10-30 1:20 ` Alistair Tonner [this message]
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=200310292020.08103.Alistair@nerdnet.ca \
--to=alistair@nerdnet.ca \
--cc=JALaramie@Loudoun-Fairfax.com \
--cc=dagent.geo@yahoo.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