> > >flow-tools > NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.73 "> > CLASS="REFENTRY" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" > > NAME="AEN1" > CLASS="APPLICATION" >flow-tools > > > CLASS="REFNAMEDIV" > NAME="AEN6" > > >Name > CLASS="APPLICATION" >flow-tools > -- Tool set for working with NetFlow data. > CLASS="REFSECT1" > NAME="AEN10" > > >DESCRIPTION > >Flow-tools is library and a collection of programs used to collect, send, process, and generate reports from NetFlow data. The tools can be used together on a single server or distributed to multiple servers for large deployments. The flow-toools library provides an API for development of custom applications for NetFlow export versions 1,5,6 and the 14 currently defined version 8 subversions. A Perl and Python interface have been contributed and are included in the distribution. > >Flow data is collected and stored by default in host byte order, yet the files are portable across big and little endian architectures. > >Commands that utilize the network use a localip/remoteip/port designation for communication. "localip" is the IP address the host will use as a source for sending or bind to when receiving NetFlow PDU's (ie the destination address of the exporter. Configuring the "localip" to 0 will force the kernel to decide what IP address to use for sending and listen on all IP addresses for receiving. "remoteip" is the destination IP address used for sending or the expected address of the source when receiving. If the "remoteip" is 0 then the application will accept flows from any source address. The "port" is the UDP port number used for sending or receiving. When using multicast addresses the localip/remoteip/port is used to represent the source, group, and port respectively. > >Flows are exported from a router in a number of different configurable versions. A flow is a collection of key fields and additional data. The flow key is {srcaddr, dstaddr, input, output, srcport, dstport, prot, ToS}. Flow-tools supports one export version per file. > >Export versions 1, 5, 6, and 7 all maintain {nexthop, dPkts, dOctets, First, Last, flags}, ie the next-hop IP address, number of packets, number of octets (bytes), start time, end time, and flags such as the TCP header bits. Version 5 adds the additional fields {src_as, dst_as, src_mask, dst_mask}, ie source AS, destination AS, source network mask, and destination network mask. Version 7 which is specific to the Catalyst switches adds in addition to the version 5 fields {router_sc}, which is the Router IP address which populates the flow cache shortcut in the Supervisor. Version 6 which is not officially supported by Cisco adds in addition to the version 5 fields {in_encaps, out_encaps, peer_nexthop}, ie the input and output interface encapsulation size, and the IP address of the next hop within the peer. Version 1 exports do not contain a sequence number and therefore should be avoided, although it is safe to store the data as version 1 if the additional fields are not used. > >Version 8 IOS NetFlow is a second level flow cache that reduces the data exported from the router. There are currently 11 formats, all of which provide {dFlows, dOctets, dPkts, First, Last} for the key fields. > > CLASS="LITERALLAYOUT" > 8.1 - Source and Destination AS, Input and Output interface 8.2 - Protocol and Port 8.3 - Source Prefix and Input interface 8.4 - Destination Prefix and Output interface 8.5 - Source/Destination Prefix and Input/Output interface 8.9 - 8.1 + ToS 8.10 - 8.2 + ToS 8.11 - 8.3 + ToS 8.12 - 8.5 + ToS 8.13 - 8.2 + ToS 8.14 - 8.3 + ports + ToS > > >Version 8 CatIOS NetFlow appears to be a less fine grained first level flow cache. > > CLASS="LITERALLAYOUT" > 8.6 - Destination IP, ToS, Marked ToS, 8.7 - Source/Destination IP, Input/Output interface, ToS, Marked ToS, 8.8 - Source/Destination IP, Source/Destination Port, Input/Output interface, ToS, Marked ToS, > > > > >The following programs are included in the flow-tools distribution. > > CLASS="COMMAND" >flow-capture > - Collect, compress, store, and manage disk space for exported flows from a router. > > CLASS="COMMAND" >flow-cat > - Concatenate flow files. Typically flow files will contain a small window of 5 or 15 minutes of exports. Flow-cat can be used to append files for generating reports that span longer time periods. > > CLASS="COMMAND" >flow-fanout > - Replicate NetFlow datagrams to unicast or multicast destinations. Flow-fanout is used to facilitate multiple collectors attached to a single router. > > CLASS="COMMAND" >flow-report > - Generate reports for NetFlow data sets. Reports include source/destination IP pairs, source/destination AS, and top talkers. Over 50 reports are currently supported. > > CLASS="COMMAND" >flow-tag > - Tag flows based on IP address or AS #. Flow-tag is used to group flows by customer network. The tags can later be used with flow-fanout or flow-report to generate customer based traffic reports. > > CLASS="COMMAND" >flow-filter > - Filter flows based on any of the export fields. Flow-filter is used in-line with other programs to generate reports based on flows matching filter expressions. > > CLASS="COMMAND" >flow-import > - Import data from ASCII or cflowd format. > > CLASS="COMMAND" >flow-export > - Export data to ASCII or cflowd format. > > CLASS="COMMAND" >flow-send > - Send data over the network using the NetFlow protocol. > > CLASS="COMMAND" >flow-receive > - Receive exports using the NetFlow protocol without storing to disk like flow-capture. > > CLASS="COMMAND" >flow-gen > - Generate test data. > > CLASS="COMMAND" >flow-dscan > - Simple tool for detecting some types of network scanning and Denial of Service attacks. > > CLASS="COMMAND" >flow-merge > - Merge flow files in chronoligical order. > > CLASS="COMMAND" >flow-xlate > - Perform translations on some flow fields. > > CLASS="COMMAND" >flow-expire > - Expire flows using the same policy of flow-capture. > > CLASS="COMMAND" >flow-header > - Display meta information in flow file. > > CLASS="COMMAND" >flow-split > - Split flow files into smaller files based on size, time, or tags. > > CLASS="REFSECT1" > NAME="AEN59" > > >AUTHOR > >Mark Fullmer CLASS="EMAIL" >< HREF="mailto:maf@splintered.net" >maf@splintered.net >> > > > CLASS="COMMAND" >flow-merge > by Larry Lidz CLASS="EMAIL" >< HREF="mailto:ellidz@eridu.uchicago.edu" >ellidz@eridu.uchicago.edu >> > > >Patches and other contribitions by a list too long to mention here. > > CLASS="COMMAND" >flow-tools > is avalable at HREF="http://www.splintered.net/sw/flow-tools" TARGET="_top" >http://www.splintered.net/sw/flow-tools >. > >A mailing list is maintained at CLASS="EMAIL" >< HREF="mailto:flow-tools@splintered.net" >flow-tools@splintered.net >> > > > CLASS="REFSECT1" > NAME="AEN78" > > >SEE ALSO > > CLASS="APPLICATION" >flow-capture >(1) CLASS="APPLICATION" >flow-cat >(1) CLASS="APPLICATION" >flow-dscan >(1) CLASS="APPLICATION" >flow-expire >(1) CLASS="APPLICATION" >flow-export >(1) CLASS="APPLICATION" >flow-fanout >(1) CLASS="APPLICATION" >flow-filter >(1) CLASS="APPLICATION" >flow-nfilter >(1) CLASS="APPLICATION" >flow-gen >(1) CLASS="APPLICATION" >flow-header >(1) CLASS="APPLICATION" >flow-import >(1) CLASS="APPLICATION" >flow-merge >(1) CLASS="APPLICATION" >flow-print >(1) CLASS="APPLICATION" >flow-receive >(1) CLASS="APPLICATION" >flow-report >(1) CLASS="APPLICATION" >flow-send >(1) CLASS="APPLICATION" >flow-split >(1) CLASS="APPLICATION" >flow-stat >(1) CLASS="APPLICATION" >flow-tag >(1) CLASS="APPLICATION" >flow-xlate >(1) > > > >
