[ovs-dev] tool tcp-ovs-dump

Aaron Conole aconole at redhat.com
Wed Mar 1 17:57:37 UTC 2017


David Lopez Muñoz <david.lopez.munoz at ericsson.com> writes:

> Hi all,
> we are seeking a tool upon ovs-appctl ofproto/trace or an option that allows to have the following feature:

ovs-tcpdump will allow dumping an interface using tcpdump, and you can
pass -xx (or -XX) to obtain the raw bytes.

ovs-tcpundump will format the packets as acceptable arguments for
ofproto/trace

Does this meet your need?

> tcp-ovs-dump <BRIDGE> <PORT_SPEC> <... TCPDUMP OPTIONS>
>   Listen to packets captured in <INTERFACE> by using the standard command 'tcpdump' with options specified at <TCPDUMP OPTIONS>
>   being passed to the 'tcpdump'. Provide the captured packets to the ovs bridge specified by BRIDGE to the port
>   specified in PORT_SPEC to retrieve the ofproto/trace and display to the standard output.
>
>   BRIDGE     Specifies the ovs bridge
>   PORT_SPEC  A PORT_SPEC is a specification of a PORT and an optional INTERFACE, separated by colon (:)
>
>              For instance:
>                 1:tunn_398ac
>
>              The tool will listen to packets captured at the specified interface and will use
>              the correspondent port to pass the ofproto/trace with those packets. If the interface
>              is absent, then the tool will automatically generate a mirror interface to listen
>              at the correspondent port, and remove it afterwards
>
>   TCPDUMP OPTIONS
>              Every option after the main options are unparsed and passed 'as is' to the tcpdump.
>              This includes the -f option to specify filters, etc
>
> Example:
>   tcp-ovs-dump br-int 1:tunn_398ac -f icmp
>
> Do you know if such a tool exists? If not, what do you think of adding a tool like this to existing ovs toolset?
> david
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev


More information about the dev mailing list