From: R P Herrold <herrold@owlriver.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Traffic classification.
Date: Fri, 13 Sep 2002 13:02:18 +0000 [thread overview]
Message-ID: <marc-lartc-103192225310602@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103189846224051@msgid-missing>
On Wed, 11 Sep 2002, George J. Jahchan wrote:
> Are there any Linux tools to identify and report network traffic at the
> application layer (sort of an application-layer protocol sniffer)? Layer
> 2-to-4 sniffers are next to useless at identifying apps that do not use
> fixed and documented ports. Examples: Peer-to-peer apps or apps
> utilizing well known ports defined for other apps like non-http traffic
> to tcp/80, or non-ftp traffic to tcp/21, etc...
tcpflow --
packaged in RPMs, with underlying SRPM at: ftp.owlriver.com
in /pub/local/ORC/tcpflow/
comes to mind -- it allows line by line post-reconstruction
and reverse engineering of an arbitrary IP protocol. I forget
the reference site, but Google shjould reveal it.
-- Russ Herrold
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-09-13 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 13:43 [LARTC] Traffic classification George J. Jahchan
2002-09-13 13:02 ` R P Herrold [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-103192225310602@msgid-missing \
--to=herrold@owlriver.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.