From: "Jeffrey D. Brower" <jeff@pointhere.net>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: netfilter@lists.netfilter.org
Subject: Re: real-time monitor question
Date: Tue, 5 Aug 2003 14:10:41 -0400 [thread overview]
Message-ID: <042401c35b7c$e22a4840$0b02a8c0@pointhere.net> (raw)
In-Reply-To: 09B04A55822EFF4DA48D2E0BB2941D4A0192DB@wardrive.citadelcomputer.com.au
> Why not put all DROP rules into a -N DROPFILTER chain and then all DROP
rules
> created jump to this table.
This is kind of what I had in mind when I was saying the ACCEPT1 - ACCEPTn
table names (chains) for each interface so I could keep track of the ACCEPT
and DENY on an interface.
> Then what you'd have to do is write a simple program which talks to your
parallel port
No problem there.
> and lists the DROPFILTER chain and compares it's values to the previous
set
> of values gathered and do something when it sees a change.
Ah! There's the rub! I have no idea how to do that.
> C++ code is best for this as it's smaller and faster than say running a
PHP script
Agreed.
I also see your idea of using the byte count reather than the packet count.
Obviously, if the bytes denied are greater than zero, at least one packet
has been DENYed. If I use that to drive the LEDs it looks like real time
and when I look in the actual log I can have it smaller and more usefull (as
in not every packet logged).
next prev parent reply other threads:[~2003-08-05 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 1:44 real-time monitor question George Vieira
2003-08-05 18:10 ` Jeffrey D. Brower [this message]
[not found] <09B04A55822EFF4DA48D2E0BB2941D4A15C03F@wardrive.citadelcomputer.com.au>
2003-08-05 1:32 ` Jeffrey D. Brower
-- strict thread matches above, loose matches on Subject: below --
2003-08-04 17:31 Jeffrey D. Brower
2003-08-05 9:20 ` Chris Wilson
2003-08-05 18:10 ` Jeffrey D. Brower
2003-08-06 9:27 ` Chris Wilson
2003-08-06 15:49 ` Jeffrey D. Brower
2003-08-06 15:48 ` Chris Wilson
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='042401c35b7c$e22a4840$0b02a8c0@pointhere.net' \
--to=jeff@pointhere.net \
--cc=georgev@citadelcomputer.com.au \
--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