FLOW-PROFILE(1)

NAME
flow-profile - er, ah, profile flows

SYNOPSIS
flow-profile [ -c commentchar ] [ -d debuglevel ] [ -f format ] [ -h ] [ -i config ] [ -? ] [ -npP ] [ -s lowsort ] [ -S highsort ] [ -t tally ] [ -H hostprofile ]

DESCRIPTION
flow-profile generates summaries for hosts or groups of hosts based on flow records it reads from stdin.

OPTIONS
Set the comment character for headser in the output. Set the debugging level. Choose the report format. Formats include: Help! Select config file. Use names. Print header. Print percents. Sort low to high on field lowsort. Sort high to low on field highsort. Tally output.

EXAMPLES
Here's part of a sample config file:

        # comment lines ignored

        # define the inside interface (ATM to OSU)
        # 1 = AIP to OSU
        # 2 = nf ethernet
        # 3 = backup ethernet
        # 8 = vip2/50 ATM to OARnet/OSC/vBNS
        # 9 = FDDI TO TW with backup for OARnet/OSC/vBNS
        inside 1 3 4

        # define outside interface
        # ATM to OARnet/vBNS/OSC
        outside 8
        # FDDI to TW and backup for ATM
        outside 9

        range 128.146.070.001   128.146.070.001 4272
        range 128.146.024.001   128.146.024.001 4272
        range 128.146.225.001   128.146.225.001 4272
        range 128.146.216.001   128.146.216.001 4272
        range 128.146.222.001   128.146.222.001 4272
        ...
        range 164.107.005.151   164.107.005.244 0003
        range 128.146.050.240   128.146.050.244 0003

        # define these after ranges to make sure all addresses in a block
        # have range definitions

        bound 128.146.0.0 128.146.255.255
        bound 140.254.0.0 140.254.255.255
        bound 164.107.0.0 164.107.255.255
In brief, this defines the inside and outside interfaces on the router, and assigns department ID's to address ranges at OSU (4th column of the range entries).

We'd run flow-profile over a set of data like this:

        flow-cat * | flow-profile -f 0 -i config
and we'd get something like bthis:

        #name       in octets out      ?       in packets out
        0003     358627478   3423321    32    4516064   4518383
        0002    7449413327  38512040    32  410612445  44213679
        ...
which you could use to generate usage based bills, for instance.

SEE ALSO
flow-capture(1), flow-cat(1), flow-connect(1), flow-dscan(1),flow-expire(1), flow-export(1), flow-fanout(1), flow-filter(1), flow-gen(1), flow-interfaces(1), flow-print(1), flow-profile(1), flow-receive(1), flow-search(1), flow-send(1), flow-sort(1), flow-stat(1),

BUGS
None known at this time.

I need to finish writing this pod page.