.\" netsniff-ng - the packet sniffing beast .\" Copyright 2013 Daniel Borkmann. .\" Subject to the GPL, version 2. .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 \fBflowtop\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. .PP .SH COLOPHON This page is part of the Linux netsniff-ng toolkit project. A description of the project, and information about reporting bugs, can be found at http://netsniff-ng.org/. right'>2016-07-21 16:36:48 -0700 commit2358024b67fccc07b95c5d8e637927acdb8e30fa (patch) tree4374a0c81ebda706e2e2e0f9e3a2042d7042a9c9 parent350e3ac2ceb696435efbbe688e6e912801a4b8c4 (diff)
greybus: control: suppress bundle_activate() for bootrom
We always knew backward compatibility with the ES3 bootrom, which was finalised about a year ago, would be a pain. Here we go again. The bootrom does not support control requests added after it was burnt into ROM for obvious reasons. This means that we need to suppress sending the new bundle_activate() operation to any interface executing the legacy bootrom. Do so by adding a new NO_PM interface quirk (we can use the control-protocol version for this later once we bump it). Note that the interface-disable path (e.g. for power down) is already handled by the FORCED_DISABLE quirk, and that the suspend/resume paths are currently avoided by making sure that the bootrom bundle never suspends. Signed-off-by: Johan Hovold <johan@hovoldconsulting.com> Reviewed-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Tested-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Diffstat