From: Dawid Kuroczko <qnex@atlantis.ssw.krakow.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables output ?
Date: Fri, 25 Oct 2002 13:23:23 +0000 [thread overview]
Message-ID: <marc-lartc-103555227211015@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103546550927610@msgid-missing>
On Fri, 25 Oct 2002, raptor wrote:
> Chandrashekhar Rane told me about "iftop" and i thuoght probably many of
> u don't know some very handy tools laying around and not included in the
> distros which can be interestiong to u so here is the list (u should
> find them with Google 'cause don't have them at hand here) :
>
> iftop - top/tcpdump like network info
> scli - browse info on the cisco router (via SNMP)
> sntop - who is online !! polls hosts and indicate their current state.. has HTML output and can run as daemon.
> fping - ping many hosts at once...
> arping - ping but not with IP packets but with ARP requests... the best way to check conectivity even if the IP is misconfigured
> atop - top like program with patch to the kernel can display net info too.
> driftnet - capture gif,jpeg and mpeg-audio that cross over network :"))
>
> If u know any other please mail them...
dsniff? :-) http://naughty.monkey.org/~dugsong/dsniff/
A nice collection of general sniffing-related tools, like
urlsnarf -- sniffs http traffic and produces access_log style file with
all requests it has seen.
webspy -- like urlsnarf, except it remotely commands Netscape to display
sniffed urls.
tcpnice, tcpkill -- forge packets which should either slow down or kill
specified tcp connection.
...something like that. :)
q.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-25 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 13:18 [LARTC] iptables output ? raptor
2002-10-24 13:32 ` Dawid Kuroczko
2002-10-25 7:46 ` raptor
2002-10-25 13:23 ` Dawid Kuroczko [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-103555227211015@msgid-missing \
--to=qnex@atlantis.ssw.krakow.pl \
--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.