ovs-tcpdump creates switch mirror ports in the ovs-vswitchd
daemon and executes tcpdump to listen against those ports. When
the tcpdump instance exits, it then cleans up the mirror port it
ovs-tcpdump will not allow multiple mirrors for the same port. It
has some logic to parse the current configuration and prevent
The -i option may not appear multiple times.
It is important to note that under Linux based kernels, tap
devices do not receive packets unless the specific tuntap device
has been opened by an application. This requires CAP_NET_ADMIN
privileges, so the ovs-tcpdump command must be run as a user with
such permissions (this is usually a super-user).
-h--help Prints a brief help message to the console.
Prints version information to the console.
The Open vSwitch database socket connection string. The
default is unix:/usr/local/var/run/openvswitch/db.sock--dump-cmd
The command to run instead of tcpdump.
The interface for which a mirror port should be created,
and packets should be dumped.
The name of the interface which should be the destination
of the mirrored packets. The default is miINTERFACE
--span If specified, mirror all ports (optional).
This page is part of the Open vSwitch (a distributed virtual
multilayer switch) project. Information about the project can be
found at ⟨http://openvswitch.org/⟩. If you have a bug report for
this manual page, send it to firstname.lastname@example.org. This page was
obtained from the project's upstream Git repository
⟨https://github.com/openvswitch/ovs.git⟩ on 2020-12-18. (At that
time, the date of the most recent commit that was found in the
repository was 2020-12-16.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
Open vSwitch 2.11.90 ovs-tcpdump(8)