On Fri, Jul 26, 2019 at 08:18:39PM +0800, Wang Li wrote: > From: Wang Li <[email protected]> > > The problem is the ovs-tcpdump can not capture the ingress vxlan traffics > when it listens on the dpdk port, and the following dump-flows described > the details: > > ovs-tcpdump stopped: > recirc_id(0),in_port(2),packet_type(ns=0,id=0),eth(),eth_type(0x0800),ipv4(), > udp(dst=4789), packets:6, bytes:888, used:0.188s, actions:tnl_pop(6) > > ovs-tcpdump started: > recirc_id(0),in_port(2),packet_type(ns=0,id=0),eth(),eth_type(0x0800),ipv4(), > udp(dst=4789), packets:17, bytes:2516, > used:0.038s,actions:tnl_pop(6),tnl_pop(6) > > There are two tnl_pop actions here, and the ovs-tcpdump app can not capture > any > ingress vxlan traffics, in the meantime the side effect is the VM got > duplicate > packets that looks like this: > 64 bytes from 172.16.0.37: icmp_seq=1 ttl=64 time=0.132 ms > 64 bytes from 172.16.0.37: icmp_seq=1 ttl=64 time=0.132 ms (DUP!) > 64 bytes from 172.16.0.37: icmp_seq=2 ttl=64 time=0.115 ms > 64 bytes from 172.16.0.37: icmp_seq=2 ttl=64 time=0.115 ms (DUP!) > > ovs-tcpdump started with this fix: > recirc_id(0),in_port(2),packet_type(ns=0,id=0),eth(),eth_type(0x0800),ipv4(), > udp(dst=4789), packets:29, bytes:4292, used:0.330s, actions:7,tnl_pop(6) > > The root cause is the duplicate tnl_pop actions, so this fix will check if the > ingress vxlan traffics are mirrored to the specified mirror port, in that case > we should deliver the origin vxlan packets to mirror port without tnl_pop. > > Signed-off-by: Wang Li <[email protected]>
Hi Wang Li, This patch appears to have gone stale in patchwork, for one reason or another. If it is still relevant then I think it needs to be revisited, by being reposted after appropriate preparation. As such I'm marking this patch as "Deferred" in patchwork. No action is required unless there is a desire to revisit this patch. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
