On 3/14/25 16:56, Aaron Conole wrote: > When the 'mirror-to' option was conceived, it was intended to allow users > the ability to arbitrarily build their own ports to use the mirror port > rather than always using an algorithmically defined mirror port. However, > the mirror port code never accommodated a port that the user defined as > part of an OVS bridge. This could be useful for running against all kinds > of OVS specific ports.
Hi, Aaron. Thanks for working on this! Please, update the documentation with this change as well. The man page is currently written with the assumption that mirror-to is a name of a tap interface. We need to make sure that it's clearly documented that if the name of an existing OVS port is provided, there must be the same-named interface on which tcpdump can be used. For example, it should not be a regular DPDK port or a vhost-user port, as there is no way to tcpdump packets from those. AF_XDP ports are also likely not suitable. And maybe also add a NEWS entry for this new user-visible functionality. Best regards, Ilya Maximets. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
