Index of /~plonka/FlowScan/old/old
README - information about FlowScan
README - information about FlowScan
FlowScan is a system to analyze and report on flows collected using Cflowd.
This document is the FlowScan
README $Revision: 1.5 $, $Date: 2000/09/15 18:37:37 $.
I'm pleased to announce the release of FlowScan-1.003. FlowScan is a tool
to monitor and graph flow information from Cisco routers in ``near''
Amonst many other things, FlowScan optionally measures and graphs traffic
for applications such as Napster. A sample of what FlowScan can do is at:
Updated INSTALL documentation and bug fixes to installation process based
on trouble spots identified by various users.
Added the identification and measurement of PASV-mode ftp data traffic to
CampusIO report. This is now combined with the ``normal'' ftp-data traffic
and is labeled ``FTP DATA'' in the graphs.
Updated Napster config for CampusIO report so that Napster traffic will
continue to be measured even though Napster.com has moved to another
Added the ability for CampusIO report to identify outbound flows by ifIndex
number rather than just next-hop IP address. This is applicable for
institutions that simply default route outbound traffic to an ``ip
unnumbered'' interface on the border router.
Bug fix so that flowscan properly handles transition from Daylight Savings
Time in fall, when the same hour of day will occur twice for most American
users. This also includes a fix so that FlowScan understands the timezone
info that is put in the raw flow file names by cflowd when patched with my
current cflowd patch and updates the RRD files accordingly.
Fixed compatibility of CampusIO and SubNetIO reports with the current
Boulder perl modules from CPAN.
Bug fix to the graphs.mf Makefile for CampusIO report to support current
rrdtool graph argument syntax.
Bug fix so that CampusIO report will not try to identify Napster flows if
the user has not configured it to do so.
Bug fix to CampusIO report so that it counts multicast traffic properly.
Bug fix to CampusIO report so that it will create RRD files regardless of
whether or not traffic was seen for the give service. Previously the graphs
Makefile would fail in environments where some kinds of traffic didn't
exists, such as ftp-data or NNTP.
Added the ability to preserver NapUser, NapUserMaybe, and ftpPASV flows to
raw flow files in a directory of their own to facilitate research and
FlowScan is licensed under the GNU General Public License, and is available
to you at:
There are two mailing lists having to do with FlowScan:
The lists' respective archives are available at:
a general mailing list for FlowScan users.
a low-volume, restricted post mailing list to keep FlowScan users informed of news
Announcements will be ``cross-posted'' to both lists, so there's no need to
These lists are hosted by the Division of Information Technology's Network
Engineering Technology group at the University of Wisconsin - Madison. To
subscribe to either of them, send email to:
You should receive an automatic response that will request that you verify
your request to become a member of the list, to which you must reply with
the authentication information there-in. Then, in response to your reply,
you should receive a welcome message. If you have any questions about the
administrative policies of this list's manager, please contact:
If you're interested in Napster specifically, note the graph labeled ``Well
Known Services Mb/s'' here:
or, directly, here:
I have written a general document about the Napster portion of the
Some related research on Napster flows is at:
I'd like to thank the FlowScan beta testers (since September 1999), early
users, and participants in the FlowScan mailing list for their efforts and
Also, thanks to Daniel McRobb, Tobi Oetiker, and CAIDA for providing the
main tools upon which FlowScan is built, namely ``cflowd'' and ``RRDTOOL''.
Note that this document is provided `as is'. The information in it is not
warranted to be correct. Use it at your own risk.
Copyright (c) 2000 Dave Plonka <firstname.lastname@example.org>.
All rights reserved.
This document may be reproduced and distributed in its entirety (including
this authorship, copyright, and permission notice), provided that no charge
is made for the document itself.