Check host interface IP address, basic connectivity [cable on floor?], and so on.
Check “show hardware.” If the MIB stats indicate that packets are reaching the NIC MAC layer - but not VPP - see if /proc/cmdline contains “intel_iommu=on”. If it does, try removing that stanza and reboot. You can, in fact, run with the iommu enabled, but for a 101(a) simple test it’s not worth going there... HTH… Dave From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of John Wei Sent: Monday, November 6, 2017 11:00 PM To: vpp-dev <vpp-dev@lists.fd.io> Subject: [vpp-dev] Simple setup, that does not work. I followed one of the fd.io<http://fd.io> youtube demo, it is very simple, but it does not work for me. * Restart vpp * vppctl set int state GigabitEthernet13/0/0 up * vppctl set int ip address GigabitEthernet13/0/0 192.168.50.166/24<http://192.168.50.166/24> * # vppctl show int addr * GigabitEthernet13/0/0 (up): * 192.168.50.166/24<http://192.168.50.166/24> * GigabitEthernetb/0/0 (dn): * local0 (dn): * on host: ping 192.168.50.166 does not work (just hang) What is missing? I am running v17.10-release bits. John
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
