On 16.12.2019 15:27, William Tu wrote: > On Mon, Dec 16, 2019 at 5:57 AM Ilya Maximets <[email protected]> wrote: >> >> On 16.12.2019 14:43, William Tu wrote: >>> On Mon, Dec 16, 2019 at 1:41 AM Ilya Maximets <[email protected]> wrote: >>>> >>>> On 13.12.2019 21:59, William Tu wrote: >>>>> Debugging netdev-afxdp is hard because tcpdump does not work >>>>> at all, even for generic mode. ovs-tcpdump which uses port >>>>> mirroring also does not work for netdev-afxdp. >>>> >>>> Hmm. Why ovs-tcpdump doesn't work for you? It should not depend >>>> on port type. If it doesn't work we need to investigate this >>>> case and fix it because it's a very important tool. >>> >>> Because ovs-tcpdump still uses 'tcpdump' tool to capture packets, >>> (dump-cmd=tcpdump) and forward to mirror port. Since tcpdump >>> sees no packet at all when type=afxdp, there is no packets to mirror. >> >> ovs-tcpdump creates simple tap interface and mirrors all the traffic >> to it. tcpdump command is started on that tap interface (no xdp here). >> There is no difference from which port types you're mirroring the traffic. >> It works for DPDK based ports and should work for afxdp. > > I got it working using ovs-tcpdump now, thanks! > ex: ovs-tcpdump -i afxdp-p0 -n -l -w /tmp/p0.pcap
OK. So, this patch is not needed. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
