.\" netsniff-ng - the packet sniffing beast .\" Copyright 2013 Daniel Borkmann. .\" Subject to the GPL, version 2. .PP .TH FLOWTOP 8 "03 March 2013" "Linux" "netsniff-ng toolkit" .SH NAME flowtop \- top-like netfilter TCP/UDP/SCTP/DCCP/ICMP(v6) flow tracking .PP .SH SYNOPSIS .PP \fB flowtop\fR { [\fIoptions\fR] } .PP .SH DESCRIPTION .PP flowtop is a top-like connection tracking tool that can run on an end host or small home router. It is able to present TCP, UDP/UDP-lite, SCTP, DCCP, and ICMP(v6) flows that have been collected by the kernel's netfilter connection tracking framework, thus no packet capturing in user space needs to be done. .PP flowtop is able to give you a quick overview of current connections on your local system, e.g. for debugging purposes or to answer questions like: .PP * If you access website X, what other connections are being opened in the background that I'm not aware of? * What connections are active that pass one's router? * I have this proprietary binary Y, to where does it connect? * To which countries am I sending data? * Are there any suspicious background connections on my machine? * How many active connections does binary Y have? .PP The following information will be presented in flowtop's output: .PP * Application name and PID when run on local machine * Reverse DNS for source and destination * Geo-location information (country, city) * Used protocols (IPv4, IPv6, TCP, UDP, SCTP, ICMP, ...) * Flow port's service name heuristic * Transport protocol state machine information .PP In order for flowtop to work, netfilter must be active and running on your machine, thus kernel-side connection tracking is active. .PP flowtop's intention is just to get a quick look over your active connections. If you want logging support, have a look at netfilter's conntrack(8) tools instead. .PP .SH OPTIONS .PP .SS -4, --ipv4 Display IPv4 flows. That is the default when flowtop is started without any arguments. .PP .SS -6, --ipv6 Display IPv6 flows. That is the default when flowtop is started without any arguments. .PP .SS -T, --tcp Display TCP flows. That is the default when flowtop is started without any arguments. .PP .SS -U, --udp Display UDP and UDP-lite flows. .PP .SS -D, --dccp Display DCCP flows. .PP .SS -I, --icmp Display ICMP version 4 and version 6 flows. .PP .SS -S, --sctp Display SCTP flows. .PP .SS -s, --show-src Also show source information of the flow, not only destination information. .PP .SS -u, --update The built-in database update mechanism will be invoked to get Maxmind's latest database. To configure search locations for databases, the file /etc/netsniff-ng/geoip.conf contains possible addresses. Thus, to save bandwidth or for mirroring Maxmind's databases (to bypass their traffic limit policy), different hosts or IP addresses can be placed into geoip.conf, separated by a newline. .PP .SS -v, --version Show version information and exit. .PP .SS -h, --help Show user help and exit. .PP .SH USAGE EXAMPLE .PP .SS flowtop Default ncurses output for flowtop that tracks IPv4, IPv6 flows for TCP. .PP .SS flowtop -46UTDISs This example enables the maximum display options for flowtop. .PP .SH CONFIG FILES .PP Files under /etc/netsniff-ng/ can be modified to extend flowtop's service resolution and lookup information. .PP * tcp.conf - TCP port/services map * udp.conf - UDP port/services map * geoip.conf - GeoIP database mirrors .PP .SH BUGS With a fairly high rate of connection tracking updates, flowtop can become unresponsive for short periods of time while scrolling. The right fix would be to replace flowtop's connection management backend with a better design with respect to the locking approach. This is still on the "todo" list. .PP .SH LEGAL flowtop is licensed under the GNU GPL version 2.0. .PP .SH HISTORY .B flowtop was originally written for the netsniff-ng toolkit by Daniel Borkmann. It is currently maintained by Tobias Klauser and Daniel Borkmann . .PP .SH SEE ALSO .BR netsniff-ng (8), .BR trafgen (8), .BR mausezahn (8), .BR ifpps (8), .BR bpfc (8), .BR astraceroute (8), .BR curvetun (8) .PP .SH AUTHOR Manpage was written by Daniel Borkmann. only
authorLinus Torvalds <torvalds@linux-foundation.org>2016-12-12 19:56:15 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2016-12-12 19:56:15 -0800
commit9465d9cc31fa732089cd8bec9f1bdfcdc174a5ce (patch)
treefb31a0a6271b255ffe6e29b4f9eb4192253f8c7f /Documentation/x86
parente71c3978d6f97659f6c3ee942c3e581299e4adf2 (diff)
parentc029a2bec66e42e57538cb65e28618baf6a4b311 (diff)
Merge branch 'timers-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer updates from Thomas Gleixner: "The time/timekeeping/timer folks deliver with this update: - Fix a reintroduced signed/unsigned issue and cleanup the whole signed/unsigned mess in the timekeeping core so this wont happen accidentaly again. - Add a new trace clock based on boot time - Prevent injection of random sleep times when PM tracing abuses the RTC for storage - Make posix timers configurable for real tiny systems - Add tracepoints for the alarm timer subsystem so timer based suspend wakeups can be instrumented - The usual pile of fixes and updates to core and drivers" * 'timers-core-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (23 commits) timekeeping: Use mul_u64_u32_shr() instead of open coding it timekeeping: Get rid of pointless typecasts timekeeping: Make the conversion call chain consistently unsigned timekeeping_Force_unsigned_clocksource_to_nanoseconds_conversion alarmtimer: Add tracepoints for alarm timers trace: Update documentation for mono, mono_raw and boot clock trace: Add an option for boot clock as trace clock timekeeping: Add a fast and NMI safe boot clock timekeeping/clocksource_cyc2ns: Document intended range limitation timekeeping: Ignore the bogus sleep time if pm_trace is enabled selftests/timers: Fix spelling mistake "Asyncrhonous" -> "Asynchronous" clocksource/drivers/bcm2835_timer: Unmap region obtained by of_iomap clocksource/drivers/arm_arch_timer: Map frame with of_io_request_and_map() arm64: dts: rockchip: Arch counter doesn't tick in system suspend clocksource/drivers/arm_arch_timer: Don't assume clock runs in suspend posix-timers: Make them configurable posix_cpu_timers: Move the add_device_randomness() call to a proper place timer: Move sys_alarm from timer.c to itimer.c ptp_clock: Allow for it to be optional Kconfig: Regenerate *.c_shipped files after previous changes ...
Diffstat (limited to 'Documentation/x86')