This may help: https://docs.fd.io/vpp/17.10/clicmd_src_plugins_dpdk_device.html#clicmd_pcap_tx_trace
Ed On Tue, Jan 9, 2018 at 9:49 AM Mohsin Kazmi (sykazmi) <syka...@cisco.com> wrote: > Please find the response inline: > > > ------------------------------ > *From:* Holoo Gulakh <holoogul...@gmail.com> > *Sent:* Tuesday, January 9, 2018 12:22 PM > *To:* Mohsin Kazmi (sykazmi); vpp-dev@lists.fd.io > *Subject:* Re: [vpp-dev] packet capture > > there are labels like dpdk-input, ip4-input-no-checksum, > ip4-icmp-echo-request and so on. > As you know wireshark shows a single entry containing all information > about a packet OR in other words wireshark captures packet at the physical > layer. > > > ============================================================================= > Q1: Which of these labels in VPP act like wireshark?? > [mohsin] dpdk-input, af-packet-input etc. Input graph nodes which receive > frames, act like wireshark. > > Q2: How to filter packets base on that label?? I want just one entry per > packet containing all packet's info > [mohsin] you can just add single label which you know interested packet > should come from. > > i.e. trace add af-packet-input 10 > > It will start tracing from af-packet-input and will report all the > subsequent graph nodes which will process that received frame. > > ============================================================================= > > On Tue, Jan 9, 2018 at 2:41 PM, Mohsin Kazmi (sykazmi) <syka...@cisco.com> > wrote: > >> Hello Holoo, >> >> >> You can find examples of traces in VPP Uses Cases. >> >> >> Specific to VPP packet tracing, please check the following link: >> >> >> >> https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#packet_tracer >> >> >> Apart from that, debug CLI list down the commands: >> >> >> vpp# trace ? >> trace add Trace given number of packets >> trace filter filter trace output - include >> NODE COUNT | exclude NODE COUNT | none >> trace frame-queue trace frame-queue (on|off) >> vpp# >> >> I hope that it will help. >> >> -br >> Mohsin >> >> >> ------------------------------ >> *From:* vpp-dev-boun...@lists.fd.io <vpp-dev-boun...@lists.fd.io> on >> behalf of Holoo Gulakh <holoogul...@gmail.com> >> *Sent:* Tuesday, January 9, 2018 11:58 AM >> *To:* vpp-dev@lists.fd.io >> *Subject:* [vpp-dev] packet capture >> >> Hi, >> In a typical scenario, we usually use wireshark or tcpdump to capture >> input/output packets from interfaces and we can use filters to filter them >> base on different criteria such as protocol. >> My question is that : when VPP handles one interface, then this interface >> is out of kernel's control so we can't capture those packets using >> wireshark or tcpdump. >> >> =============================================== >> What is an alternative in VPP for wireshark or tcpdump?? >> =============================================== >> >> I read somewhere that there is a command named "trace" in VPP. >> Is it correct?? if so, how to use it?? how to filter packets?? what is >> the representation format of packets?? how to filter them base on network >> stack layers?? >> I want to use this tool for debugging my scenarios which uses VPP as >> dataplane. >> > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
