Free netflow software for linux

DB based NetFLow Collector aims to collect Cisco NetFlow data and store it to a database.
DB based NetFlow Collector has a plugin interface, which makes it flexible for fitting in particular tasks.
Enhancements:
- First release. post your comments/bug reports.

OSSP flow2rrd is a companion tool to the Flow-Tools toolkit for storing NetFlow network traffic data in an accumulating fixed-size RRDTool Round-Robin-Database (RRD) for visualization purposes.
This file is piece of OSSP flow2rrd, a tool for storing NetFlow data into an RRD which can be found at http://www.ossp.org/pkg/tool/flow2rrd/.
Enhancements:
- Created the initial version of OSSP flow2rrd.

bbnfc is useful for debugging netflow exports as produced by Cisco, Juniper, etc. routers. This simple program sits on a user-specified UDP port and displays to stdout all netflow exports that are sent to the machine. Complete program is 300 lines long (C source).

The source should compile under most flavours of UNIX, with little or no modification.
Note: Some web browsers will tend to display .tgz archives on the screen rather than saving them to a file. You may need to hold down the shift key when selecting the link below (or possibly some other brain-dead combination).


In this archive you will see the following files:
readme.bbnfc - This readme file
bbnfc.c - Source code for bbnfc
netflow.h - Header file
bbnfc - Pre-compiled binary for Linux (Intel)

To compile from source the following (or some variation thereof) should work:
gcc -o bbnfc bbnfc.c

Basic usage instructions can be obtained with
./bbnfc -h

cflowd is a flow analysis tool currently used for analyzing Ciscos NetFlow enabled switching method.

The current release (described below) includes the collections, storage, and basic analysis modules for cflowd and for arts++ libraries. This analysis package permits data collection and analysis by ISPs and network engineers in support of capacity planning, trends analysis, and characterization of workloads in a network service provider environment. Other areas where cflowd may prove useful are: tracking for Web hosting, accounting and billing, network planning and analysis, network monitoring, developing user profiles, data warehousing and mining, as well as security-related investigations.


cflowd is no longer supported by CAIDA. Instead, please consider the use of flow-tools, which will provide a toolset for working with NetFlow data. flow-tools can also be used (like cflowd) in conjunction with FlowScan, maintained by Dave Plonka at the University of Wisconsin, Madison.

Stager is a system for aggregating and presenting network statistics. Stager project is generic and can be customized to present and process any kind of network statistics.
The backend collects data and stores reports in a database, automatically handling the aggregation of hourly statistics into days, weeks, and months.
The Web frontend presents data in tables, matrices, or plots. The reports are fully customizable, and their definitions are stored in the database.
Installation:
If you are upgrading from a previous version of Stager, see the UPGRADE file.
This version of Stager only support Netflow. Future releases will also support roundtrip measurements, SNMP and various passive monitoring measurements.
To run Stager you now need PHP4 CLI with SNMP support. Under debian you can just install php4-cli and php4-snmp
Backend:
1. Create a new Postgresql user that is allowed to create new databases
2. Create a new user that runs the Stager backend. The rest of the installation should be done as this user
3. /stager-install.pl --type=backend --backends=netflow --path=/installation/path/
4. Edit /installation/path/etc/netflow.cfg and /installation/path/etc/getRouterInfo.cfg
5. cd /installation/path/bin
6. ./db_install.pl --backend=netflow
7. Default access control is to give full access to admin user and limited access to guest users. Check /installation/path/lib/getRouterInfo.custom.php if you want to change this.
8. ./getRouterInfo.php -v -v -o
9. ./get-netflow.pl -v --no-missing --delete-old Check for error messages
10. Edit /installation/path/bin/getRouterInfo.sh
11. Edit crontab:
30 0-23/2 * * * $HOME/stager/bin/getRouterInfo.sh -v //How often you run this command depends on how dynamic your network is
45 * * * * $HOME/stager/bin/get-netflow.pl --delete-old
50 1 * * * $HOME/stager/bin/aggregate.pl --backend=netflow --interval=1 day --no-distributed --manual-mode
45 2 * * 1 $HOME/stager/bin/aggregate.pl --backend=netflow --interval=1 week --timeformat YYYY-IW --no-cap --no-distributed
50 2 1 * * $HOME/stager/bin/aggregate.pl --backend=netflow --interval=1 month --timeformat YYYY-MM --no-distributed
Frontend:
1. ./stager-install.pl --type=frontend --path=/installation/path
2. edit /installation/path/config/user.config.php
Whats New in 2.0.1 Stable Release:
- This release fixes several bugs in both the frontend and backend.
- The most important fix is that bookmarks with relative times are now working properly.
- This means that if you create a report that shows data, for example, for the last hour with available data, you can now create a bookmark that will always show data for the last hour with available data.
Whats New in 3.0 Beta 1 Development Release:
- The backend has been completely rewritten and is now implemented in PHP.
- The new backend is faster and more generic so that it is easier to add support for other types of statistics.
- The new backends are also more robust against database down time.
- In the web GUI, it is now possible to right click on most data to bring up a context menu where it is possible to add custom links.

flow-tools is a set of programs for processing and managing NetFlow exports from Cisco and Juniper routers. The tools included are: flow-capture, flow-cat, flow-dscan, flow-expire, flow-export, flow-fanout, flow-filter, flow-gen, flow-header, flow-import, flow-mask, flow-merge, flow-nfilter, flow-print, flow-receive, flow-report, flow-send, flow-split, flow-stat, flow-tag, and flow-xlate.

Flow data is collected and stored by default in host byte ordera nd the files are portable across every 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 PDUs (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.

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.

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.

flow-capture - Collect, compress, store, and manage disk space for exported flows from a router.
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.
flow-fanout - Replicate NetFlow datagrams to unicast or multicast destinations. Flow-fanout is used to facilitate multiple collectors attached to a single router.
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.
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.
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.
flow-import - Import data from ASCII or cflowd format.
flow-export - Export data to ASCII or cflowd format.
flow-send - Send data over the network using the NetFlow protocol.
flow-receive - Receive exports using the NetFlow protocol without storing to disk like flow-capture.
flow-gen - Generate test data.
flow-dscan - Simple tool for detecting some types of network scanning and Denial of Service attacks.
flow-merge - Merge flow files in chronoligical order.
flow-xlate - Perform translations on some flow fields.
flow-expire - Expire flows using the same policy of flow-capture.
flow-header - Display meta information in flow file.
flow-split - Split flow files into smaller files based on size, time, or tags.

Monitoring API project is a multi-user programming interface designed to simplify the development of network monitoring software and allows users to express their monitoring needs in a device-independent way.
The main abstraction provided by MAPI is the network flow. Although flows have been used before in network monitoring systems, MAPI gives flows a first-class status. Applications that uses MAPI can specify what flows or flow statistics they are interested in by applying functions to flows.
A MAPI function can be a BPF filter, string search, packet counter or more advanced like a NetFlow generator. These function will automatically run in hardware if there is support for it on the hardware being used.
MAPI currently supports the following hardware:
- Normal NICs through libpcap
- DAG cards without co-processor
- SCAMPI adapter
Enhancements:
- This release includes support for distributed monitoring, several new MAPI functions, demo applications, and a lot of bugfixes.