View source for VPP/Progressive VPP Tutorial

== Exercise: Setting up your environment ==

All of these exercises are designed to be performed on an Ubuntu 16.04 (Xenial) box.

If you have an Ubuntu 16.04 box on which you have sudo, you can feel free to use that.

If you do not, a Vagrantfile is provided to setup a basic Ubuntu 16.04 box for you

=== Vagrant Set up ===

==== Action: Install Virtualbox ====

If you do not already have virtualbox on your laptop (or if it is not up to date), please download and install it:

https://www.virtualbox.org/wiki/Downloads

==== Action: Install Vagrant ====

If you do not already have Vagrant on your laptop (or if it is not up to date), please download it:

https://www.vagrantup.com/downloads.html

==== Action: Create a Vagrant Directory ====

Create a directory on your laptop:

<pre style="background-color:palegreen">
mkdir fdio-tutorial
cd fdio-tutorial/
</pre>

Create a Vagrantfile containing:

<pre>
# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure(2) do |config|

  config.vm.box = "puppetlabs/ubuntu-16.04-64-nocm"
  config.vm.box_check_update = false

  vmcpu=(ENV['VPP_VAGRANT_VMCPU'] || 2)
  vmram=(ENV['VPP_VAGRANT_VMRAM'] || 4096)

  config.ssh.forward_agent = true

  config.vm.provider "virtualbox" do |vb|
      vb.customize ["modifyvm", :id, "--ioapic", "on"]
      vb.memory = "#{vmram}"
      vb.cpus = "#{vmcpu}"
      #support for the SSE4.x instruction is required in some versions of VB.
      vb.customize ["setextradata", :id, "VBoxInternal/CPUM/SSE4.1", "1"]
      vb.customize ["setextradata", :id, "VBoxInternal/CPUM/SSE4.2", "1"]
  end
end
</pre>

==== Action: Vagrant Up ====

Bring up your Vagrant VM:

<pre style="background-color:palegreen">
vagrant up
</pre>

==== Action: ssh to Vagrant VM ====

<pre style="background-color:palegreen">
vagrant ssh
</pre>

== Exercise: Install vpp ==

=== Skills to be learned ===

# Learn how to install vpp binary packges using apt-get.

'''Note''': This tutorial is using a special packaging of vpp called vpp_lite that allows you to run multiple vpp processes simultaneously.  We will be building topologies of these vpp processes to allow us to perform labs which require multiple instances of 'routers' or 'switches'.  Because of this, we will be getting our vpp packages from a slightly non-standard apt repository.

The installation mechanism is very similar to the standard [[VPP/Installing_VPP_binaries_from_packages|Install VPP from Binary Packages]] instructions.

=== Action: Add key for apt repo ===

<pre style="background-color:palegreen">
curl -L https://packagecloud.io/fdio/tutorial/gpgkey | sudo apt-key add -
</pre>

=== Action: Add repo to apt sources.list.d ===

With your favorite text editor (and sudo), create a file:

<pre style="background-color:palegreen">
/etc/apt/sources.list.d/fdio_tutorial.list
</pre>

containing

<pre>
deb https://packagecloud.io/fdio/tutorial/ubuntu/ xenial main
deb-src https://packagecloud.io/fdio/tutorial/ubuntu/ xenial main
</pre>

=== Action: apt-get install vpp ===

Run 

<pre style="background-color:palegreen">
sudo apt-get update
sudo apt-get install vpp
</pre>

== Exercise: vpp basics ==

=== Skills to be Learned===

By the end of the exerise you should be able to:
# Run a vpp instance in a mode which allows multiple vpp processes to run
# Issue vpp commands from the unix shell
# Run a vpp shell and issue it commands


=== vpp command learned in this exercise ===

# [https://docs.fd.io/vpp/17.04/clicmd_src_vpp_app.html#clicmd_show_version show ver]

=== Action: Run vpp ===

vpp runs in userspace.  In a production environment you will often run it with DPDK to connect to real NICs or vhost to connect to VMs.
In those circumstances you usually run a single instance of vpp.

For purposes of this tutorial, it is going to be extremely useful to run multiple instances of vpp, and connect them to each other to form
a topology.  Fortunately, vpp supports this.

When running multiple vpp instances, each instance needs to have specified a 'name' or 'prefix'.  In the example below, the 'name' or 'prefix' is "vpp1"

<pre style="background-color:palegreen">
sudo vpp api-segment { prefix vpp1 }
</pre>

Example Output:
<pre style="background-color:Khaki">
unix_physmem_init: use huge pages
vlib_plugin_early_init:230: plugin path /usr/lib/vpp_plugins
0: api_main_init:52: vam 6acb60
</pre>

=== Action: Using vppctl to send commands to vpp ===

You can send vpp commands with a utility called <pre>vppctl</pre>.

When running vppctl against a named version of vpp, you will need to run:

<pre>
sudo vppctl -p ${name} ${cmd}
</pre>

So to run 'show ver' against the vpp instance named vpp1 you would run:

<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show ver
</pre>
Output:
<pre style="background-color:Khaki">
vpp v17.04-rc0~177-g006eb47 built by ubuntu on fdio-ubuntu1604-sevt at Mon Jan 30 18:30:12 UTC 2017
</pre>


=== Action: Using vppctl to start a vpp shell ===
You can also use vppctl to launch a vpp shell with which you can run multiple vpp commands interactively by running:

<pre>
sudo vppctl -p ${name}
</pre>

which will give you a command prompt.

Try doing show ver that way:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1
vpp1# show ver
</pre>

Output:
<pre style="background-color:Khaki">
vpp v17.04-rc0~177-g006eb47 built by ubuntu on fdio-ubuntu1604-sevt at Mon Jan 30 18:30:12 UTC 2017

vpp1#
</pre>

== Exercise: Create an Interface ==

=== Skills to be Learned ===

# Create a veth interface in Linux host
# Assign an IP address to one end of the veth interface in the Linux host
# Create a vpp host-interface that connected to one end of a veth interface via AF_PACKET
# Add an ip address to a vpp interface
# Setup a 'trace'
# View a 'trace'
# Clear a 'trace'
# Verify using ping from host
# Ping from vpp
# Examine Arp Table
# Examine ip fib

=== vpp command learned in this exercise ===
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_devices_af_packet.html#clicmd_create_host-interface create host-interface]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet.html#clicmd_set_interface_state set int state]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_ip.html#clicmd_set_interface_ip_address set int ip address]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet.html#clicmd_show_hardware-interfaces show hardware]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet.html#clicmd_show_interfaces show int]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet.html#clicmd_show_interfaces show int addr]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vlib.html#clicmd_trace_add trace add]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vlib.html#clicmd_clear_trace clear trace]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_ip.html#clicmd_ping ping]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_ethernet.html#clicmd_show_ip_arp show ip arp]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_fib.html#clicmd_show_ip_fib show ip fib]

=== Initial State ===
The initial state here is presumed to be the final state from the exercise [[VPP/Progressive_VPP_Tutorial#Exercise:_vpp_basics| VPP Basics]]

=== Action: Create veth interfaces on host ===

In Linux, there is a type of interface call 'veth'.  Think of a 'veth' interface as being an interface that has two ends to it (rather than one).

Create a veth interface with one end named '''vpp1out''' and the other named '''vpp1host'''
<pre style="background-color:palegreen">
sudo ip link add name vpp1out type veth peer name vpp1host
</pre>

Turn up both ends:
<pre style="background-color:palegreen">
sudo ip link set dev vpp1out up
sudo ip link set dev vpp1host up
</pre>

Assign an IP address
<pre style="background-color:palegreen">
sudo ip addr add 10.10.1.1/24 dev vpp1host
</pre>

Display the result:
<pre style="background-color:palegreen">
sudo ip addr show vpp1host
</pre>

Example Output:
<pre style="background-color:Khaki">
10: vpp1host@vpp1out: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5e:97:e3:41:aa:b8 brd ff:ff:ff:ff:ff:ff
    inet 10.10.1.1/24 scope global vpp1host
       valid_lft forever preferred_lft forever
    inet6 fe80::5c97:e3ff:fe41:aab8/64 scope link 
       valid_lft forever preferred_lft forever
</pre>

=== Action: Create vpp host- interface ===

Create a host interface attached to '''vpp1out'''.
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 create host-interface name vpp1out
</pre>

Output:

<pre style="background-color:Khaki">
host-vpp1out

</pre>

Confirm the interface:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show hardware
</pre>

Example Output:
<pre style="background-color:Khaki">
              Name                Idx   Link  Hardware
host-vpp1out                       1     up   host-vpp1out
  Ethernet address 02:fe:48:ec:d5:a7
  Linux PACKET socket interface
local0                             0    down  local0
  local

</pre>


Turn up the interface:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 set int state host-vpp1out up
</pre>

Confirm the interface is up:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show int
</pre>

<pre style="background-color:Khaki">
              Name               Idx       State          Counter          Count     
host-vpp1out                      1         up       
local0                            0        down
</pre>

Assign ip address 10.10.1.2/24
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 set int ip address host-vpp1out 10.10.1.2/24
</pre>

Confirm the ip address is assigned:

<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show int addr
</pre>

<pre style="background-color:Khaki">
host-vpp1out (up):
  10.10.1.2/24
local0 (dn):
</pre>

=== Action: Add trace ===

<pre style="background-color:palegreen">
sudo vppctl -p vpp1 trace add af-packet-input 10
</pre>

=== Action: Ping from host to vpp ===

<pre style="background-color:palegreen">
ping -c 1 10.10.1.2
</pre>

<pre style="background-color:Khaki">
PING 10.10.1.2 (10.10.1.2) 56(84) bytes of data.
64 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=0.557 ms

--- 10.10.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.557/0.557/0.557/0.000 ms
</pre>

=== Action: Examine Trace of ping from host to vpp ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show trace
</pre>

<pre style="background-color:Khaki">
------------------- Start of thread 0 vpp_main -------------------
Packet 1

00:09:30:397798: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 42 snaplen 42 mac 66 net 80
      sec 0x588fd3ac nsec 0x375abde7 vlan 0 vlan_tpid 0
00:09:30:397906: ethernet-input
  ARP: fa:13:55:ac:d9:50 -> ff:ff:ff:ff:ff:ff
00:09:30:397912: arp-input
  request, type ethernet/IP4, address size 6/4
  fa:13:55:ac:d9:50/10.10.1.1 -> 00:00:00:00:00:00/10.10.1.2
00:09:30:398191: host-vpp1out-output
  host-vpp1out
  ARP: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50
  reply, type ethernet/IP4, address size 6/4
  02:fe:48:ec:d5:a7/10.10.1.2 -> fa:13:55:ac:d9:50/10.10.1.1

Packet 2

00:09:30:398227: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd3ac nsec 0x37615060 vlan 0 vlan_tpid 0
00:09:30:398295: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:09:30:398298: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x9b46
    fragment id 0x894c, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x83c
00:09:30:398300: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x9b46
    fragment id 0x894c, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x83c
00:09:30:398303: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x9b46
      fragment id 0x894c, flags DONT_FRAGMENT
    ICMP echo_request checksum 0x83c
00:09:30:398305: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x9b46
    fragment id 0x894c, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x83c
00:09:30:398307: ip4-icmp-echo-request
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x9b46
    fragment id 0x894c, flags DONT_FRAGMENT
  ICMP echo_request checksum 0x83c
00:09:30:398317: ip4-load-balance
  fib 0 dpo-idx 10 flow hash: 0x0000000e
  ICMP: 10.10.1.2 -> 10.10.1.1
    tos 0x00, ttl 64, length 84, checksum 0xbef3
    fragment id 0x659f, flags DONT_FRAGMENT
  ICMP echo_reply checksum 0x103c
00:09:30:398318: ip4-rewrite
  tx_sw_if_index 1 dpo-idx 2 : ipv4 via 10.10.1.1 host-vpp1out: IP4: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50 flow hash: 0x00000000
  IP4: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50
  ICMP: 10.10.1.2 -> 10.10.1.1
    tos 0x00, ttl 64, length 84, checksum 0xbef3
    fragment id 0x659f, flags DONT_FRAGMENT
  ICMP echo_reply checksum 0x103c
00:09:30:398320: host-vpp1out-output
  host-vpp1out
  IP4: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50
  ICMP: 10.10.1.2 -> 10.10.1.1
    tos 0x00, ttl 64, length 84, checksum 0xbef3
    fragment id 0x659f, flags DONT_FRAGMENT
  ICMP echo_reply checksum 0x103c
</pre>

=== Action: Clear trace buffer ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 clear  trace
</pre>

=== Action: ping from vpp to host ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 ping 10.10.1.1
</pre>
<pre style="background-color:Khaki">
64 bytes from 10.10.1.1: icmp_seq=1 ttl=64 time=.0865 ms
64 bytes from 10.10.1.1: icmp_seq=2 ttl=64 time=.0914 ms
64 bytes from 10.10.1.1: icmp_seq=3 ttl=64 time=.0943 ms
64 bytes from 10.10.1.1: icmp_seq=4 ttl=64 time=.0959 ms
64 bytes from 10.10.1.1: icmp_seq=5 ttl=64 time=.0858 ms

Statistics: 5 sent, 5 received, 0% packet loss
</pre>

=== Action: Examine Trace of ping from vpp to host ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show trace
</pre>

<pre style="background-color:Khaki">
------------------- Start of thread 0 vpp_main -------------------
Packet 1

00:12:47:155326: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd471 nsec 0x161c61ad vlan 0 vlan_tpid 0
00:12:47:155331: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:47:155334: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2604
    fragment id 0x3e8f
  ICMP echo_reply checksum 0x1a83
00:12:47:155335: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2604
    fragment id 0x3e8f
  ICMP echo_reply checksum 0x1a83
00:12:47:155336: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x2604
      fragment id 0x3e8f
    ICMP echo_reply checksum 0x1a83
00:12:47:155339: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2604
    fragment id 0x3e8f
  ICMP echo_reply checksum 0x1a83
00:12:47:155342: ip4-icmp-echo-reply
  ICMP echo id 17572 seq 1
00:12:47:155349: error-drop
  ip4-icmp-input: unknown type

Packet 2

00:12:48:155330: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd472 nsec 0x1603e95b vlan 0 vlan_tpid 0
00:12:48:155337: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:48:155341: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2565
    fragment id 0x3f2e
  ICMP echo_reply checksum 0x7405
00:12:48:155343: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2565
    fragment id 0x3f2e
  ICMP echo_reply checksum 0x7405
00:12:48:155344: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x2565
      fragment id 0x3f2e
    ICMP echo_reply checksum 0x7405
00:12:48:155346: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2565
    fragment id 0x3f2e
  ICMP echo_reply checksum 0x7405
00:12:48:155348: ip4-icmp-echo-reply
  ICMP echo id 17572 seq 2
00:12:48:155351: error-drop
  ip4-icmp-input: unknown type

Packet 3

00:12:49:155331: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd473 nsec 0x15eb77ef vlan 0 vlan_tpid 0
00:12:49:155337: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:49:155341: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x249e
    fragment id 0x3ff5
  ICMP echo_reply checksum 0xf446
00:12:49:155343: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x249e
    fragment id 0x3ff5
  ICMP echo_reply checksum 0xf446
00:12:49:155345: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x249e
      fragment id 0x3ff5
    ICMP echo_reply checksum 0xf446
00:12:49:155349: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x249e
    fragment id 0x3ff5
  ICMP echo_reply checksum 0xf446
00:12:49:155350: ip4-icmp-echo-reply
  ICMP echo id 17572 seq 3
00:12:49:155354: error-drop
  ip4-icmp-input: unknown type

Packet 4

00:12:50:155335: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd474 nsec 0x15d2ffb6 vlan 0 vlan_tpid 0
00:12:50:155341: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:50:155346: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2437
    fragment id 0x405c
  ICMP echo_reply checksum 0x5b6e
00:12:50:155347: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2437
    fragment id 0x405c
  ICMP echo_reply checksum 0x5b6e
00:12:50:155350: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x2437
      fragment id 0x405c
    ICMP echo_reply checksum 0x5b6e
00:12:50:155351: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x2437
    fragment id 0x405c
  ICMP echo_reply checksum 0x5b6e
00:12:50:155353: ip4-icmp-echo-reply
  ICMP echo id 17572 seq 4
00:12:50:155356: error-drop
  ip4-icmp-input: unknown type

Packet 5

00:12:51:155324: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 98 snaplen 98 mac 66 net 80
      sec 0x588fd475 nsec 0x15ba8726 vlan 0 vlan_tpid 0
00:12:51:155331: ethernet-input
  IP4: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:51:155335: ip4-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x23cc
    fragment id 0x40c7
  ICMP echo_reply checksum 0xedb3
00:12:51:155337: ip4-lookup
  fib 0 dpo-idx 5 flow hash: 0x00000000
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x23cc
    fragment id 0x40c7
  ICMP echo_reply checksum 0xedb3
00:12:51:155338: ip4-local
    ICMP: 10.10.1.1 -> 10.10.1.2
      tos 0x00, ttl 64, length 84, checksum 0x23cc
      fragment id 0x40c7
    ICMP echo_reply checksum 0xedb3
00:12:51:155341: ip4-icmp-input
  ICMP: 10.10.1.1 -> 10.10.1.2
    tos 0x00, ttl 64, length 84, checksum 0x23cc
    fragment id 0x40c7
  ICMP echo_reply checksum 0xedb3
00:12:51:155343: ip4-icmp-echo-reply
  ICMP echo id 17572 seq 5
00:12:51:155346: error-drop
  ip4-icmp-input: unknown type

Packet 6

00:12:52:175185: af-packet-input
  af_packet: hw_if_index 1 next-index 4
    tpacket2_hdr:
      status 0x20000001 len 42 snaplen 42 mac 66 net 80
      sec 0x588fd476 nsec 0x16d05dd0 vlan 0 vlan_tpid 0
00:12:52:175195: ethernet-input
  ARP: fa:13:55:ac:d9:50 -> 02:fe:48:ec:d5:a7
00:12:52:175200: arp-input
  request, type ethernet/IP4, address size 6/4
  fa:13:55:ac:d9:50/10.10.1.1 -> 00:00:00:00:00:00/10.10.1.2
00:12:52:175214: host-vpp1out-output
  host-vpp1out
  ARP: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50
  reply, type ethernet/IP4, address size 6/4
  02:fe:48:ec:d5:a7/10.10.1.2 -> fa:13:55:ac:d9:50/10.10.1.1
</pre>

After examinging the trace, clear it again.

=== Action: Examine arp tables ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show ip arp
</pre>
<pre style="background-color:Khaki">
    Time           IP4       Flags      Ethernet              Interface       
    570.4092    10.10.1.1      D    fa:13:55:ac:d9:50       host-vpp1out      
</pre>

=== Action: Examine routing table ===
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show ip fib
</pre>
<pre style="background-color:Khaki">
ipv4-VRF:0, fib_index 0, flow hash: src dst sport dport proto 
0.0.0.0/0
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:0 buckets:1 uRPF:0 to:[0:0]]
    [0] [@0]: dpo-drop ip4
0.0.0.0/32
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:1 buckets:1 uRPF:1 to:[0:0]]
    [0] [@0]: dpo-drop ip4
10.10.1.1/32
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:10 buckets:1 uRPF:9 to:[5:420] via:[1:84]]
    [0] [@5]: ipv4 via 10.10.1.1 host-vpp1out: IP4: 02:fe:48:ec:d5:a7 -> fa:13:55:ac:d9:50
10.10.1.0/24
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:8 buckets:1 uRPF:7 to:[0:0]]
    [0] [@4]: ipv4-glean: host-vpp1out
10.10.1.2/32
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:9 buckets:1 uRPF:8 to:[6:504]]
    [0] [@2]: dpo-receive: 10.10.1.2 on host-vpp1out
224.0.0.0/4
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:3 buckets:1 uRPF:3 to:[0:0]]
    [0] [@0]: dpo-drop ip4
240.0.0.0/4
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:2 buckets:1 uRPF:2 to:[0:0]]
    [0] [@0]: dpo-drop ip4
255.255.255.255/32
  unicast-ip4-chain
  [@0]: dpo-load-balance: [index:4 buckets:1 uRPF:4 to:[0:0]]
    [0] [@0]: dpo-drop ip4
</pre>

== Exercise: Connecting two vpp instances ==

=== Skills to be Learned ===
You should be able to perform this exercise with the following skills learned in previous exercises:
# Create a veth interface in Linux host
# Create a vpp host-interface that connected to one end of a veth interface via AF_PACKET
# Add an ip address to a vpp interface
# Ping from vpp

=== Initial state ===

The initial state here is presumed to be the final state from the exercise [[VPP/Progressive_VPP_Tutorial#Exercise:_Create_an_Interface| Create an Interface]]

=== Running a second vpp instances ===
You should already have a vpp instance running named: vpp1.

Run a second vpp instance named: vpp2.

=== Create veth interface on host to connect the two vpp instances ===

Create a veth interface on the Linux host with one 
end named '''vpp1vpp2''' and the other named '''vpp2vpp1'''.  

Don't assign an ip address to either
end on the host.

=== Create vpp host interfaces ===

Create a host interface on vpp1 connected to '''vpp1vpp2'''.  Assign it the address '''10.10.2.1/24'''

Create a host interface on vpp2 connected to '''vpp2vpp1'''. Assign it the address '''10.10.2.2/24'''

=== Running a second vpp instances ===

Run a second instanced of vpp named '''vpp2'''.

=== Create veth interface on host to connect the two vpp instances ===

Using skills from the previous exercise, create a veth interface on the host with one 
end named vpp1vpp2 and the other named vpp2vpp1.  Don't assign an ip address to either
end on the host.

=== Create vpp host interfaces ===

Using skills from the previous exercise, create a host interface on vpp1 connected to vpp1vpp2.  Assign it the address 10.10.2.1/30
Using skills from the previous exercise, create a host interface on vpp2 connected to vpp2vpp1. Assign it the address 10.10.2.2/30

=== Ping from vpp1 to vpp2 ===

Ping 10.10.2.2 from vpp1

Ping 10.10.2.1 from vpp2

== Exercise: Routing ==

=== Skills to be Learned ===
In this exercise you will learn these new skills:
# Add route to Linux Host routing table
# Add route to vpp routing table

And revisit the old ones:
# Examine vpp routing table
# Enable trace on vpp1 and vpp2
# ping from host to vpp
# Examine and clear trace on vpp1 and vpp2
# ping from vpp to host
# Examine and clear trace on vpp1 and vpp2

=== vpp command learned in this exercise ===

# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_ip.html#clicmd_ip_route ip route add]

=== Initial State ===
The initial state here is presumed to be the final state from the exercise [[VPP/Progressive_VPP_Tutorial#Connecting_two_vpp_instances| Connecting two vpp instances]]

=== Action: Setup host route ===

<pre style="background-color:palegreen">
sudo ip route add 10.10.2.0/24 via 10.10.1.2
ip route
</pre>

<pre style="background-color:Khaki">
default via 10.0.2.2 dev enp0s3 
10.0.2.0/24 dev enp0s3  proto kernel  scope link  src 10.0.2.15 
10.10.1.0/24 dev vpp1host  proto kernel  scope link  src 10.10.1.1 
10.10.2.0/24 via 10.10.1.2 dev vpp1host 
</pre>

=== Setup return route on vpp2 ===

<pre style="background-color:palegreen">
sudo vppctl -p vpp2 ip route add 10.10.1.0/24  via 10.10.2.1
</pre>

=== Ping from host through vpp1 to vpp2 ===

# Setup a trace on vpp1 and vpp2
# Ping 10.10.2.2 from the host
# Examine the trace on vpp1 and vpp2
# Clear the trace on vpp1 and vpp2

=== Ping from vpp2 through vpp1 to host ===
# Setup the trace on vpp1 and vpp2
# Ping 10.10.1.1 from vpp2
# Examine the trace on vpp1 and vpp2
# Clear the trace on vpp1 and vpp2

== Exercise: Switching ==

=== Skills to be Learned ===

# Associate an interface with a bridge domain
# Create a loopback interaface
# Create a BVI (Bridge Virtual Interface) for a bridge domain
# Examine a bridge domain

=== vpp command learned in this exercise ===

# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html#clicmd_show_bridge-domain show bridge]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html#clicmd_show_bridge-domain show bridge detail]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html#clicmd_set_interface_l2_bridge set int l2 bridge]
# [https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html#clicmd_show_l2fib show l2fib verbose]

=== Initial state  ===

Unlike previous exercises, for this one you want to start tabula rasa.

Note: You will lose all your existing config in your vpp instances!

To clear existing config from previous exercises run:

<pre style="background-color:palegreen">
ps -ef | grep vpp | awk '{print $2}'| xargs sudo kill
sudo ip link del dev vpp1host
sudo ip link del dev vpp1vpp2
</pre>

=== Action: Run vpp instances ===

# Run a vpp instance named '''vpp1'''
# Run a vpp instance named '''vpp2'''

=== Action: Connect vpp1 to host ===

# Create a veth with one end named vpp1host and the other named vpp1out.
# Connect vpp1out to vpp1
# Add ip address 10.10.1.1/24 on vpphost
 
=== Action: Connect vpp1 to vpp2 ===

# Create a veth with one end named vpp1vpp2 and the other named vpp2vpp1.
# Connect vpp1vpp2 to vpp1.
# Connect vpp2vpp2 to vpp1.

=== Action: Configure Bridge Domain on vpp1 ===

Check to see what bridge domains already exist, and select the first bridge domain number not in use:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show bridge-domain
</pre>

<pre style="background-color:Khaki">
  ID   Index   Learning   U-Forwrd   UU-Flood   Flooding   ARP-Term     BVI-Intf   
  0      0        off        off        off        off        off        local0    
</pre>

In the example above, there is bridge domain ID '0' already, so we will create bridge domain 1.

Add host-vpp1out to bridge domain ID 1
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 set interface l2 bridge host-vpp1out 1
</pre>

Add host-vpp1vpp2 to bridge domain ID1
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 set int l2 bridge host-vpp1vpp2  1
</pre>

Examine bridge domain 1:
<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show bridge-domain 1 detail
</pre>

<pre style="background-color:Khaki">
  ID   Index   Learning   U-Forwrd   UU-Flood   Flooding   ARP-Term     BVI-Intf   
  1      1        on         on         on         on         off          N/A     

           Interface           Index  SHG  BVI  TxFlood        VLAN-Tag-Rewrite       
         host-vpp1out            1     0    -      *                 none             
         host-vpp1vpp2           2     0    -      *                 none
</pre>

===Action: Configure loopback interface on vpp2 ===

<pre style="background-color:palegreen">
sudo vppctl -p vpp2 create loopback interface
</pre>

<pre style="background-color:Khaki">
loop0
</pre>

Add the ip address 10.10.1.2/24 to vpp2 interface loop0.
Set the state of interface loop0 on vpp2 to 'up'

=== Action: Configure bridge domain on vpp2 ===

Check to see the first available bridge domain ID (it will be 1 in this case)

Add interface loop0 as a bvi interface to bridge domain 1

<pre style="background-color:palegreen">
sudo vppctl -p vpp2 set int l2 bridge loop0 1 bvi
</pre>

Add interface vpp2vpp1 to bridge domain 1
<pre style="background-color:palegreen">
sudo vppctl -p vpp2 set int l2 bridge host-vpp2vpp1  1
</pre>

Examine the bridge domain and interfaces.

=== Action: Ping from host to vpp and vpp to host ===

# Add trace on vpp1 and vpp2
# ping from host to 10.10.1.2
# Examine and clear trace on vpp1 and vpp2
# ping from vpp2 to 10.10.1.1
# Examine and clear trace on vpp1 and vpp2

=== Action: Examine l2 fib ===

<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show l2fib verbose
</pre>
<pre style="background-color:Khaki">
    Mac Address     BD Idx           Interface           Index  static  filter  bvi   Mac Age (min) 
 de:ad:00:00:00:00    1            host-vpp1vpp2           2       0       0     0      disabled    
 c2:f6:88:31:7b:8e    1            host-vpp1out            1       0       0     0      disabled    
2 l2fib entries
</pre>

<pre style="background-color:palegreen">
sudo vppctl -p vpp2 show l2fib verbose
</pre>
<pre style="background-color:Khaki">
    Mac Address     BD Idx           Interface           Index  static  filter  bvi   Mac Age (min) 
 de:ad:00:00:00:00    1                loop0               2       1       0     1      disabled    
 c2:f6:88:31:7b:8e    1            host-vpp2vpp1           1       0       0     0      disabled    
2 l2fib entries
</pre>

== Source NAT ==

=== Initial state  ===

Unlike previous exercises, for this one you want to start tabula rasa.

Note: You will lose all your existing config in your vpp instances!

To clear existing config from previous exercises run:

<pre style="background-color:palegreen">
ps -ef | grep vpp | awk '{print $2}'| xargs sudo kill
sudo ip link del dev vpp1host
sudo ip link del dev vpp1vpp2
</pre>

=== Action: Install vpp-plugins ===

Snat is supported by a plugin, so vpp-plugins need to be installed

<pre style="background-color:palegreen">
sudo apt-get install vpp-plugins
</pre>

=== Action: Create vpp instance ===

Create one vpp instance named vpp1.

Confirm snat plugin is present:

<pre style="background-color:palegreen">
sudo vppctl -p vpp1 show plugins
</pre>

<pre style="background-color:Khaki">
 Plugin path is: /usr/lib/vpp_plugins
 Plugins loaded: 
  1.ioam_plugin.so
  2.ila_plugin.so
  3.acl_plugin.so
  4.flowperpkt_plugin.so
  5.snat_plugin.so
  6.libsixrd_plugin.so
  7.lb_plugin.so
</pre>