From: George Chacon <please.help.me@comcast.net>
To: Eric Leblond <eleblond@init-sys.com>,
Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: RE: How to keep record of repeat attackers?
Date: Thu, 13 Mar 2003 07:46:30 -0800 [thread overview]
Message-ID: <PKEJLPJCFBFLJJPHMGPIEEBHCAAA.please.help.me@comcast.net> (raw)
In-Reply-To: <1047547166.8677.15.camel@tech004.alphalink.fr>
Accessing the netfilter logs in a web browser on a separate computer sounds
perfect. That's exactly what I'm looking for. Thank you for the
information.
George Chacon
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org]On Behalf Of Eric Leblond
Sent: Thursday, March 13, 2003 1:19 AM
To: Netfilter Mailing List
Subject: RE: How to keep record of repeat attackers?
On Thu, 2003-03-13 at 09:50, George Chacon wrote:
> Wow! I'm guessing you've been using iptables for a while. I thank you
for
> the thorough response. I'll take it and slowly examine it a line and word
> at a time - and do further research on some of the terms. I'll also take
a
> look at http://ntop.org. It does look pretty nice.
You can use ulog-php which is an web interface to ulog netfilter logs.
It give you useful stats as most often blocked hosts ...
The homepage is : http://home.regit.org/ulogd-php.html
a demo site is available at
http://home.regit.org/ulog-demo/
It may be the kind of thing you want.
</end self_add>
--
Eric Leblond <eleblond@init-sys.com>
Init-Sys
next prev parent reply other threads:[~2003-03-13 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 1:20 How to keep record of repeat attackers? George Chacon
2003-03-13 3:24 ` Joel Newkirk
2003-03-13 7:19 ` George Chacon
2003-03-13 7:40 ` Joel Newkirk
2003-03-13 8:50 ` George Chacon
2003-03-13 9:19 ` Eric Leblond
2003-03-13 15:46 ` George Chacon [this message]
2003-03-13 19:34 ` Bill Davidsen
2003-03-13 20:29 ` Aldo S. Lagana
-- strict thread matches above, loose matches on Subject: below --
2003-03-14 16:50 George Chacon
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=PKEJLPJCFBFLJJPHMGPIEEBHCAAA.please.help.me@comcast.net \
--to=please.help.me@comcast.net \
--cc=eleblond@init-sys.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