From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] logging traffic on port/remote host/localhost
Date: Mon, 10 Feb 2003 05:48:34 +0000 [thread overview]
Message-ID: <marc-lartc-104485618123316@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104485482022504@msgid-missing>
Alex,
: I want to add some logging so that I can got back and see exactly what
: traffic I had when latency was bad. I want to see what internal hosts
: and external host were generating the traffic. What ports they were
: talking on, what protocols etc.
:
: I know how to add logging in iptables but reading the logs is kind of
: tiresome. I rather have something like iptraf but that can be run
: after the fact.
You definitely want to visit Stef Coene's site [1] and have a look first
at his GUI tools [2] and possibly also some of his monitoring scripts. [3]
Don't forget about ntop, which (in its "new" incarnation) collects
statistical data you can examine after the fact. [4]
There are others interested in the same sort of (general) question, also
on this mailing list. [5]
And if you are comfortable with your current iptables commands, why not
consider the iptacct tool. [6]
Good luck,
-Martin
[1] http://www.docum.org/
[2] http://www.docum.org/stef.coene/qos/gui/
[3] http://www.docum.org/stef.coene/qos/monitor/
[4] http://www.ntop.org/ntop.html
[5] http://mailman.ds9a.nl/pipermail/lartc/2002q4/005752.html
[6] http://tretmine.org/iptacct/
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-02-10 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 5:25 [LARTC] logging traffic on port/remote host/localhost Alex Polite
2003-02-10 5:48 ` Martin A. Brown [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=marc-lartc-104485618123316@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.