flowrate man page on DragonFly

Man page or keyword search:  
man Server   44335 pages
apropos Keyword Search (all sections)
Output format
DragonFly logo
[printable version]

flowrate(3)			SiLK Tool Suite			   flowrate(3)

NAME
       flowrate - SiLK plug-in providing payload and rate filters and fields

SYNOPSIS
	 rwfilter --plugin=flowrate.so [--payload-bytes=INTEGER_RANGE]
	       [--payload-rate=DECIMAL_RANGE]
	       [--bytes-per-second=DECIMAL_RANGE]
	       [--packets-per-second=DECIMAL_RANGE] ...

	 rwcut --plugin=flowrate.so --fields=FIELDS ...

	 rwgroup --plugin=flowrate.so --fields=FIELDS ...

	 rwsort --plugin=flowrate.so --fields=FIELDS ...

	 rwstats --plugin=flowrate.so --fields=FIELDS --values=FIELDS ...

	 rwuniq --plugin=flowrate.so --fields=FIELDS --values=FIELDS ...

DESCRIPTION
       When loaded into rwfilter(1), the flowrate plug-in provides switches
       that can partition flows based on bytes of payload and/or on the rates
       of data transfer.

       For rwcut(1), rwgroup(1), rwsort(1), rwstats(1), and rwuniq(1), the
       flowrate plug-in provides fields that will print, sort flows by, and
       group flows by the bytes of payload, bytes-per-packet, bytes-per-
       second, packets-per-second, and bytes of payload per second.  The
       flowrate plug-in also provides aggregate value fields in rwstats and
       rwuniq.

       The payload byte count is determined by subtracting from the total byte
       count in the flow the bytes of overhead used by the packet headers.
       The payload calculation assumes minimal packet headers---that is, there
       are no options in the packets.  For TCP, the switch assumes there are
       no TCP timestamps in the packets.  Thus, the calculated payload will be
       the maximum possible bytes of payload.  If the packet-overhead is
       larger than the reported number of bytes, the value is zero.

       The various flow-rate quantities are determined by dividing the payload
       byte count, packet count, or byte count by the duration of the flow,
       giving the average rate across the flow.	 When the flow's reported
       duration is zero, a duration of one second is assumed (that is, the
       count is used directly).

       The flowrate plug-in must be explicitly loaded into an application via
       the --plugin switch.  The reason for this is due to name clashes with
       existing switches and fields.  For example, adding the
       --packets-per-second switch to rwfilter means any short-cutting of the
       current --packets switch will fail.

OPTIONS
       The flowrate plug-in provides the following options to the indicated
       applications.

   rwfilter Switches
       When the flowrate plug-in has been loaded, the following set of
       partitioning switches are added to rwfilter.  To pass the filter, the
       record must pass the test implied by each switch.  The form of the
       argument to each switch is described below.  The partitioning switches
       are:

       --payload-bytes=INTEGER_RANGE
	   Check whether the payload byte count is within INTEGER_RANGE.

       --payload-rate=DECIMAL_RANGE
	   Check whether the average number of payload bytes seen per second
	   in the flow is within DECIMAL_RANGE.

       --packets-per-second=DECIMAL_RANGE
	   Check whether the average number of packets per second in the flow
	   is within DECIMAL_RANGE.

       --bytes-per-second=DECIMAL_RANGE
	   Check whether the average number of bytes per second in the flow is
	   within DECIMAL_RANGE.

       An INTEGER_RANGE is a range of two non-negative integers, and a
       DECIMAL_RANGE is a range of two non-negative decimal values with
       accuracy up to 0.0001.  The ranges are specified as two values
       separated by a hyphen, MIN-MAX; for example "1-500" or "5.0-10.031".
       If a single value is given (e.g., 3.14), the range consists of that
       single value.  The upper limit of the range may be omitted, such as
       "1-", in which case the upper limit is set to the maximum possible
       value.

   rwcut, rwgroup, rwsort, rwstats, and rwuniq Switches
       --fields=FIELDS
	   FIELDS refers to a list of fields to use for the operation.	The
	   flowrate plug-in adds the following fields for display, sorting,
	   and grouping using the rwcut(1), rwgroup(1), rwsort(1), rwstats(1),
	   and rwuniq(1) tools:

	   payload-bytes
	       Print, sort by, or group by the number of bytes of payload.

	   payload-rate
	       Print, sort by, or group by the bytes of payload seen per
	       second.

	   pckts/sec
	       Print, sort by, or group by the packets seen per second.

	   bytes/sec
	       Print, sort by, or group by the bytes seen per second.

	   bytes/packet
	       Print, sort by, or group by the average number of bytes
	       contained in each packet.

       --values=AGGREGATES
	   The flowrate plug-in adds the following aggregate value fields to
	   rwstats and rwuniq.	AGGREGATES refers to a list of values to
	   compute for each bin.  To compute these values, flowrate maintains
	   separate sums for the numerator and denominator while reading the
	   records, then flowrate computes the ratio when the output is
	   generated.

	   payload-bytes
	       Compute the approximate bytes of payload for records in this
	       bin.

	   payload-rate
	       Compute the average bytes of payload seen per second for
	       records in this bin.

	   pckts/sec
	       Compute the average packets seen per second for records in this
	       bin,

	   bytes/sec
	       Compute the average bytes seen per second for records in this
	       bin.

	   bytes/packet
	       Compute the average number of bytes contained in each packet
	       for records in this bin.

ENVIRONMENT
       SILK_PATH
	   This environment variable gives the root of the install tree.  When
	   searching for plug-ins, a SiLK application may use this environment
	   variable.  See the "FILES" section for details.

       SILK_PLUGIN_DEBUG
	   When set to 1, the SiLK applications print status messages to the
	   standard error as they attempt to find and open the flowrate.so
	   plug-in.  A typical invocation using this variable is:

	    env SILK_PLUGIN_DEBUG=1 rwcut --plugin=flowrate.so --version

FILES
       ${SILK_PATH}/lib64/silk/flowrate.so
       ${SILK_PATH}/lib64/flowrate.so
       ${SILK_PATH}/lib/silk/flowrate.so
       ${SILK_PATH}/lib/flowrate.so
       /usr/local/lib64/silk/flowrate.so
       /usr/local/lib64/flowrate.so
       /usr/local/lib/silk/flowrate.so
       /usr/local/lib/flowrate.so
	   Possible locations for the plug-in.

SEE ALSO
       rwcut(1), rwfilter(1), rwgroup(1), rwsort(1), rwstats(1), rwuniq(1),
       silk(7)

SiLK 3.11.0.1			  2016-02-19			   flowrate(3)
[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net