Hi Andrew, I failed to try the vpp ping today. Is it broken?
My testbed is quite simple: vpp < --- > host I can ping vpp from host. However, I failed to ping host from vpp. And I captured the echo request packets sent by vpp, looks like they are malformed. The data filed of ICMP Data is filled with 0, where we should have valid icmp id/seq, etc. I attached the pcap in the mail. Any clues? Thanks, Wenxian On Wed, Nov 2, 2016 at 5:06 AM, Andrew 👽 Yourtchenko <ayour...@gmail.com> wrote: > Hi, > > When I was writing the ping code I had noticed ip probe was already > broken because its registration of the ICMP code via the magic > initialization function happens before the magic initialization function of > the ICMP module is called which then zeroizes all the registrations. > > So I just proceeded to implement the ping which happens to not have the > same problem (maybe due to alphabet order!), and simultaneously keep an eye > if anyone actually uses the ip probe function at all (it's IPv4 only) > > So for troubleshooting purpose please use ping rather than IP probe - but > if you need ip probe function, please nudge me back! :) > > Hope this helps ! > > --a > > On 28 Oct 2016, at 19:12, Shravan Ambati <shravan.amb...@calix.com> wrote: > > Hi, > > > > I am new to vpp. I was following this tutorial - > https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP > > I was able to ping from the host to the Vpp VM as per the tutorial. > > I can see the echo request/reply packets in the dpdk-input trace as well. > > But when I do ip probe on vpp command line to the host IP it fails – > > > > vpp# ip probe 172.29.X.XXX GigabitEthernet0/8/0 > > ip probe-neighbor: Resolution failed for 172.29.X.XXX > > > > > > fib table shows packets for only two entries – > > > > vpp# show ip fib > > Table 0, fib_index 0, flow hash: src dst sport dport proto > > Destination Packets Bytes Adjacency > > 172.29.0.0/22 1248 116694 weight 1, index 3 > > arp > GigabitEthernet0/8/0 172.29.X.XXX/22 > > > > > > > > > > 172.29.X.XXX(Ip of GigabitEthernet0/8/0 )/32 > 44 3256 weight 1, index 4 > > local 172.29.3.164/22 > > > > > > > > Any pointers on why the ip probe on Vpp fails? > > > > Thanks > > Shravan > > _______________________________________________ > 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 >
echo_req.pcap
Description: Binary data
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
