JNETTOP(8)

💖 JNETTOP 💖

okay bestie, so this is the manual page for jnettop — that's the (8) section of the System Manager's Manual, the sysadmin corner, you know the vibe 💅

Fair warning though: this manual page is OBSOLETE. Like, for real. The manpage itself literally says so. Please run jnettop -h as your main source of info about usage. Our girl -h is the real main character here, periodt. 👑

---

✨ NAME ✨

jnettop — view hosts/ports taking up the most network traffic 🦋

---

🌸 SYNOPSIS 🌸

jnettop [options] [-i interface] [-d filename] [-f filename] [-x rule]

---

🎀 DESCRIPTION 🎀

This manual page documents briefly the jnettop command. And, okay, saying it again because it matters: this manual page is OBSOLETE. Please use jnettop -h as a main source of information about usage. (The manpage knows it's outdated, she's self-aware, we love that for her 😭)

So here's the tea ☕: jnettop captures traffic coming across the host it is running on, and then displays streams sorted by the bandwidth they use. The result is a nice listing of communication on the network by host and port — how many bytes went through this transport, and the bandwidth it is consuming. Literally so satisfying to watch. 🔥

---

💅 OPTIONS 💅

These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-`). A summary of options is included below. ✨

• -h, --help — show summary of options. (the icon, the moment, the goat 🐐)
• -v, --version — show version of program.
• -c, --content-filter — disable content filtering. yes this option turns it OFF, be mindful bestie 🙈
• -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.
• -i, --interface name — capture packets on specified interface.
• --local-aggr [none|host|port|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|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 enclose the filter into quotes when running from a shell. (quotes are not optional, she WILL yell at you 💀)

---

🌈 CONFIGURATION 🌈

Program looks for settings in the file specified by parameter -f, which defaults to ~/.jnettop. The configuration file is an ordinary text file with keywords and their arguments. You HAVE to enclose arguments into double quotes. Like, you HAVE to. Capital letters, bestie, that's how serious she is. 😤

Available keywords are:

• interface "<interface_name>" — the interface keyword specifies network interface on which to start listening. Example:

interface "eth0"

• local_aggregation [none|host|port|host+port] — the local_aggregation keyword specifies initial active local aggregation. Valid values are none, host, port, and host+port. Example:

local_aggregation host

• promisc [on|off] — the promisc keyword specifies whether jnettop captures packets in promiscuous mode. Example:

promisc on

• remote_aggregation [none|host|port|host+port] — the remote_aggregation keyword specifies initial active remote aggregation. Valid values are none, host, port, and host+port. Example:

remote_aggregation port

• resolve [on|off] — the resolve keyword specifies whether resolving is performed on the IP addresses or not.

resolve off

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

resolve_rule "192.168.0.0" "255.255.255.0" normal
resolve_rule "192.168.0.0" "255.255.255.0" external "/usr/share/jnettop/jnettop-lookup-nbm"

• 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:

rule "show 192.168.1.32" "src 192.168.1.32"

• select_rule "<rule_name>" — the select_rule keyword specifies the initial active predefined rule. The rule must be defined before this keyword is used. Example:

select_rule "show 192.168.1.32"

• 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:

variable "intranet" "net 192.168.0.0/16 or 10.0.0.0/8 or 172.16.0.0/12"

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

---

🫶 AUTHOR 🫶

This manual page was originally written by Ari Pollak <ari@debian.org>, for the Debian GNU/Linux system. Small changes were introduced by Jakub Skopal <j@kubs.cz>.

---

and that's the whole page, bestie!! 🎀 this one's from the System Manager's Manual, dated April 8, 2006 — yes, 2006, she's vintage, she's iconic, she's got lore. go run jnettop -h for the real real, mwah 💋✨🌈