Dear Neale, your guess was right.
With ping it works fine and vpp does not crash. I was using prove because is suggested by the official wiki in order to test the interface, therefore I would suggest to replace it also in the wiki. Thanks for the prompt answer. Best regards, Alessio On Wed, May 24, 2017 at 8:17 PM, Neale Ranns (nranns) <nra...@cisco.com> wrote: > > > Hi Alessio, > > > > My guess is the probe command caused VPP to crash, and since your running > it as a deamon, it restarted with your previous configs gone. > > > > The probe command sends an ARP request to the address in question, so > don’t probe your own address, instead probe a peer’s. These days we also > have ‘ping’ which is more useful. > > > > Regards, > > neale > > > > *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Alessio Silvestro < > ale.silver...@gmail.com> > *Date: *Wednesday, 24 May 2017 at 17:20 > *To: *"vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io> > *Subject: *[vpp-dev] VPP interface configuration problem > > > > Dear all, > > > > I use the vagrant installation. > > > > I can start the VM, build the packages and start vpp process. > > > > I am stuck at the step (Step 1: Configure and enable an interface) of the > guide available at https://wiki.fd.io/view/VPP/Build,_install,_and_test_ > images. > > > > At the first boot I have: > > > > vagrant@localhost:/$ ifconfig > > enp0s3 Link encap:Ethernet HWaddr 08:00:27:33:82:8a > > inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0 > > inet6 addr: fe80::a00:27ff:fe33:828a/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:376 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:290 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:34649 (34.6 KB) TX bytes:29047 (29.0 KB) > > > > enp0s8 Link encap:Ethernet HWaddr 08:00:27:1e:20:8b > > inet addr:172.28.128.5 Bcast:172.28.128.255 Mask:255.255.255.0 > > inet6 addr: fe80::a00:27ff:fe1e:208b/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:5907 (5.9 KB) TX bytes:1482 (1.4 KB) > > > > enp0s9 Link encap:Ethernet HWaddr 08:00:27:da:51:35 > > inet addr:172.28.128.6 Bcast:172.28.128.255 Mask:255.255.255.0 > > inet6 addr: fe80::a00:27ff:feda:5135/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:20 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:5907 (5.9 KB) TX bytes:1482 (1.4 KB) > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:65536 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1 > > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > > > > I selected enp0s9 as target interface, thus: > > > > sudo ifconfig enp0s9 down > > sudo ip addr flush dev enp0s9 > > sudo stop vpp > > sudo start vpp > > > > Therefore, I configure the interface for VPP. Its name is > GigabitEthernet0/9/0. > > > > sudo vppctl set int ip address GigabitEthernet0/9/0 172.28.128.6/24 > (the IP address is the same of the one shown by ifconfig in the beginning) > > sudo vppctl set int state GigabitEthernet0/9/0 up > > > > Now I can see this: > > > > vagrant@localhost:/$ sudo vppctl show int address > > GigabitEthernet0/9/0 (up): > > 172.28.128.6/24 > > local0 (dn): > > > > > > So, it looks to me that it is correctly configured. > > > > However when I do this: > > > > sudo vppctl ip probe 172.28.128.6 GigabitEthernet0/9/0 > > exec error: Misc > > > > I got this error and the interface is down and without an IP address > assigned. > > sudo vppctl show int address > > GigabitEthernet0/9/0 (dn): > > local0 (dn): > > > > > > Do I do something wrong, or what is it happening? > > > > Thanks in advance for any help. > > > > Best regards, > > Alessio > >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
