Hi John, Could you please provide a packet trace from VPP whilst it is unresponsive.
Thanks, neale From: <vpp-dev-boun...@lists.fd.io> on behalf of John Wei <johnt...@gmail.com> Date: Friday, 3 November 2017 at 20:20 To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] Can't ping VPP int addr, until VPP int ping outside first I have configured tow interface within VPP # vppctl show int addr GigabitEthernet13/0/0 (up): 192.168.50.166/24<http://192.168.50.166/24> GigabitEthernetb/0/0 (up): 192.168.50.201/24<http://192.168.50.201/24> gre0 (up): gre1 (up): On a different node, on the same subnet (192.168.50.151), I was not able to get ping response from 166, until I did a "vppctl ping 192.168.50.151." ## on 192.168.50.151 # ping 192.168.50.166 PING 192.168.50.166 (192.168.50.166) 56(84) bytes of data. From 192.168.50.151 icmp_seq=1 Destination Host Unreachable << delete repeated message> From 192.168.50.151 icmp_seq=23 Destination Host Unreachable From 192.168.50.151 icmp_seq=24 Destination Host Unreachable << On VPP node, did a vppctl ping 192.168.50.151>> 64 bytes from 192.168.50.166<http://192.168.50.166>: icmp_seq=27 ttl=64 time=0.498 ms 64 bytes from 192.168.50.166<http://192.168.50.166>: icmp_seq=28 ttl=64 time=0.435 ms 64 bytes from 192.168.50.166<http://192.168.50.166>: icmp_seq=29 ttl=64 time=0.316 ms 64 bytes from 192.168.50.166<http://192.168.50.166>: icmp_seq=30 ttl=64 time=0.469 ms Any guess what I may have done wrong? Or, this is a v17.10 bug? John
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
