NAME

SYNOPSIS

DESCRIPTION

jnettop captures traffic coming across the host it is running on and displays streams sorted by bandwidth they use. Result is a nice listing of communication on network by host and port, how many bytes went through this transport and the bandwidth it is consuming.

OPTIONS

-h, --help

Show summary of options.

-v, --version

Show version of program.

-b, --bit-units

show BPS In bits per second, not bytes per second

-c, --content-filter

disable content filtering

-d, --debug filename

write debug information into file

-f, --config-file filename

reads configuration from filename. defaults to ~/.jnettop. an example can be found at /usr/share/doc/jnettop/dot.jnettop. or in .jnettop file from original distribution package.

-i, --interface name

capture packets on specified interface

--local-aggr [none|host|port]

set local aggregation to specified value

-n, --no-resolver

disable resolving of ip addresses

-p, --promiscuous

enables promiscuous mode on the sniffed interface

--remote-aggr [none|host|port]

set remote aggregation to specified value

-s, --select-rule name

selects one of the rules defined in .jnettop configuration file (by it's name)

-x, --filter rule

allows for specification of custom filtering rule. this allows for tcpdump(1) style syntax. don't forget to enclolse the filter into quotes when running from a shell.

CONFIGURATION

interface "<interface_name>"

The interface keyword specifies network interface on which to start listening. Example:

local_aggregation [none|host|port]

The local_aggregation keyword specifies initial active local aggregation. Valid values are none, host and port. Example:

promisc [on|off]

The promisc keyword specifies, whether jnettop captures packets in promiscuous mode. Example:

remote_aggregation [none|host|port]

The remote_aggregation keyword specifies initial active remote aggregation. Valid values are none, host and port. Example:

resolve [on|off]

The resolve keyword specifies, whether resolving is performed on the IP addresses or not.

resolve_rule "<network address>" "<network mask>" [normal|external] (<arguments> ...)

The resolve_rule keyword adds one resolver into list of resolvers for specified address. When resolving, jnettop examines all the rules in the order how they were specified in configuration file. If the network address matches specified range, declared resolver is used. Resolver can be normal, which means the standard DNS lookup or external, which executes specified external program to perform resolving. This can be used with bundled jnettop-lookup-nmb script, which looks up IP addresses using nmblookup(1) tool. If a tool returns empty string or DNS is not found, next rule is examined. If jnettop runs out of rules, than the standard DNS lookup is executed.

rule "<rule_name>" "<rule_definition>"

The rule keyword defines a set of predefined tcpdump(1)-like filters to apply. You can specify various filters as "show me what 192.168.1.32" sends:

select_rule "<rule_name>"

The select_rule keyword specifies initial active predefined rule. The rule must be defined before this keyword is used. Example:

variable "<variable_name>" "<variable_contents>"

The variable keyword introduces a string variable for use in future rule definitions. It can be used to shorten rule definitions. Example:

For more information, see README file or .jnettop example configuration file included in distribution.

AUTHOR