blob: eb6aa2fdebc2fa6047f03a2ecfab5aca9a5a854d [file] [log] [blame]
Keith Burns (alagalah)e0965d42016-06-19 07:58:51 -07001VPP has now been built, installed, and started.
2
3To give it a spin, we can create a tap interface and try a simple ping
4(with trace).
5
6Make sure you have run:
7
8$ vagrant ssh
9
10To get to the vagrant VM:
11
12vagrant@localhost:~$
13
14Confirm that vpp is running with
15
16vagrant@localhost:~$ sudo status vpp
17vpp start/running, process 25202
18
19To create the tap:
20
21vagrant@localhost:~$ sudo vppctl tap connect foobar
22Created tap-0 for Linux tap 'foobar'
23vagrant@localhost:~$ sudo vppctl show int
24
25To assign it an ip address (and 'up' the interface):
26
27vagrant@localhost:~$ sudo vppctl set int ip address tap-0 192.168.1.1/24
28vagrant@localhost:~$ sudo vppctl set int state tap-0 up
29
30To turn on packet tracing for the tap interface:
31vagrant@localhost:~$ sudo vppctl trace add tapcli-rx 10
32
33Now, to set up and try the other end:
34vagrant@localhost:~$ sudo ip addr add 192.168.1.2/24 dev foobar
35vagrant@localhost:~$ ping -c 3 192.168.1.1
36
37To look at the trace:
38vagrant@localhost:~$ sudo vppctl show trace
39
40And to stop tracing:
41
42vagrant@localhost:~$ sudo vppctl clear trace
43
44Other fun things to look at:
45
46The vlib packet processing graph:
47vagrant@localhost:~$ sudo vppctl show vlib graph
48
49which will produce output like:
50
51 Name Next Previous
52ip4-icmp-input error-punt [0] ip4-local
53 ip4-icmp-echo-request [1]
54 vpe-icmp4-oam [2]
55
56To read this, the first column (Name) is the name of the node.
57The second column (Next) is the name of the children of that node.
58The third column (Previous) is the name of the parents of this node.
59
60To see this README again:
61cat /vagrant/README