LinuxCommandLibrary

flow

Type checker for JavaScript programs

TLDR

Run a flow check

$ flow
copy

Check which files are being checked by flow
$ flow ls
copy

Run a type coverage check on all files in a directory
$ flow batch-coverage --show-all --strip-root [path/to/directory]
copy

Display line-by-line type coverage stats
$ flow coverage --color [path/to/file.jsx]
copy

SYNOPSIS

flow [options] [capture_file]

PARAMETERS

-h
    Display help message and exit.

-v
    Be verbose. Prints information about the input file.

-n
    Process only number of packets/records.

-c
    Count records.

-x
    Print records in hexadecimal format.

-p
    Print decoded packet data.

-r
    Print a specific record number.

-f
    Apply a BPF-style filter expression.

DESCRIPTION

The flow command is a tool used to analyze and display network flow data captured from network devices such as routers and switches. It allows users to examine the details of network traffic, including source and destination IP addresses, ports, protocols, and the amount of data transferred.

It reads flow records from a capture file or standard input. This data is typically collected using flow monitoring tools like NetFlow, sFlow, or IPFIX.

The command offers various options for filtering and formatting the output to focus on specific types of traffic or display relevant information. Analyzing network flow data can help identify network bottlenecks, security threats, and usage patterns.

CAVEATS

The flow command is heavily reliant on the input file format being correctly formatted flow data (NetFlow, sFlow, IPFIX). The accuracy of the analysis is limited by the quality of the captured data.

INPUT FILE FORMATS

The flow command supports various network flow data formats, including NetFlow v5/v9, sFlow, and IPFIX. The specific formats supported may vary depending on the implementation of the command.

HISTORY

The history of flow command isn't well documented as a standalone general purpose command in the typical linux distributions. It's often part of larger network analysis suites and varies depending on the implementation. It likely evolved alongside the development and adoption of network flow monitoring technologies like NetFlow and sFlow to provide a way to analyze collected data.

SEE ALSO

tcpdump(1), wireshark(1), nfdump(1)

Copied to clipboard