OVS-TCPDUMP(8)
π
OVS-TCPDUMP β the ovs-tcpdump page, bestie edition π
okay so you're reading the Open vSwitch manual page for ovs-tcpdump (that's the OVS-TCPDUMP(8) section of the manual, iykyk) and honestly? it's a good one. let's get into it β¨
π¦ NAME π¦
ovs-tcpdump β dump traffic from an Open vSwitch port using tcpdump. that's the whole vibe. you point it at a port, it snitches on the packets. no cap π
πΈ SYNOPSIS πΈ
ovs-tcpdump -i <port> <tcpdump options>...
π DESCRIPTION π
so here's the tea: ovs-tcpdump creates switch mirror ports in the ovs-vswitchd daemon and then executes tcpdump to listen against those ports. when the tcpdump instance exits, it cleans up the mirror port it created. responsible queen behavior, honestly π
ovs-tcpdump will not allow multiple mirrors for the same port. it has some logic to parse the current configuration and prevent duplicate mirrors. it's giving bodyguard energy π«Ά
The -i option may not appear multiple times. one port, one mirror. periodt.
β οΈ important bestie moment: under Linux-based kernels, tap devices do not receive packets unless the specific tuntap device has been opened by an application. this requiresCAP_NET_ADMINprivileges, so theovs-tcpdumpcommand must be run as a user with such permissions (this is usually a super-user). so likeβ¦ sudo, basically. don't come for me, it's just the rules π
β¨ OPTIONS β¨
-h,--helpβ prints a brief help message to the console. little helpful angel π-V,--versionβ prints version information to the console. who are you? what version are you? main character questions π--db-sock <socket>β the Open vSwitch database socket connection string. the default isunix:<rundir>/db.sock. that's the default, don't forget it π--dump-cmd <command>β the command to run instead oftcpdump. yes, you can swap out the star of the show, iconic behavior honestly π-i,--interfaceβ the interface for which a mirror port should be created, and packets should be dumped. this is the port you're obsessed with π--mirror-toβ the name of the interface which should be the destination of the mirrored packets. if the specified interface does not exist, it will be created as part of the setup process. if the interface already exists, it must be a port type that can be used with thetcpdumputility. mirror ports cannot be used for normal traffic. the default value ismi<port>. lowkey a whole little lifecycle going on here π¦--spanβ if specified, mirror all ports (optional). all of them. every single one. go big or go home π₯--filter <flow>β if specified, only mirror packets that match the provided OpenFlow filter. the available fields are documented inovs-fields(7). selective attention, we love to see it β
π SEE ALSO π
ovs-appctl(8), ovs-vswitchd(8), ovs-pcap(1), ovs-fields(7), ovs-tcpundump(1), tcpdump(8), wireshark(8). the whole friend group fr fr π«Ά
π AUTHOR π
The Open vSwitch Development Community. legends only.
π COPYRIGHT π
2016-2024, The Open vSwitch Development Community
π and that's the page!! this one's from Open vSwitch version 3.6, dated Feb 13, 2026 β go dump some packets, bestie, you're gonna slay π β¨πΈ
π¦ where this page comes from
- fedora 43: openvswitch-test 3.6.2-1.fc43 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms