VPP/Installing VPP binaries from packages

From fd.io
Jump to: navigation, search


If you are simply using vpp, it can be convenient to simply install the packages. The instructions below will pull the latest freshest package build from the master branch (updated on every merge).

Package Descriptions

  • vpp - Description: Vector Packet Processing--executables. This package provides VPP executables: vpp, vpp_api_test, vpp_json_test
    • vpp - the vector packet engine
    • vpp_api_test - vector packet engine API test tool
    • vpp_json_test - vector packet engine JSON test tool
  • vpp-lib - Description: Vector Packet Processing--runtime libraries. This package contains the VPP shared libraries, including:
    • vppinfra - foundation library supporting vectors, hashes, bitmaps, pools, and string formatting.
    • svm - vm library
    • vlib - vector processing library
    • vlib-api - binary API library
    • vnet - network stack library
  • vpp-plugins - Description: Vector Packet Processing--plugin modules
    • acl
    • dpdk
    • flowprobe
    • gtpu
    • ixge
    • kubeproxy
    • l2e
    • lb
    • memif
    • nat
    • pppoe
    • sixrd
    • stn
  • vpp-dbg - Description: Vector Packet Processing--debug symbols
  • vpp-dev - Description: Vector Packet Processing--development support. This package contains development support files for the VPP libraries
  • vpp-api-java - Description: JAVA binding for the VPP Binary API.
  • vpp-api-python - Description: Python binding for the VPP Binary API.
  • vpp-api-lua - Description: Lua binding for the VPP Binary API.


Packages are published for both the amd64 (Intel) and aarch64 (ARM) architectures. The packages are stored in the same repository so no special action is required to select your architecture.

Add fd.io repo

VPP release packages are available at: https://packagecloud.io/fdio/release

Note to VPP Committers: Pre-release packages are staged for final verification at: https://packagecloud.io/fdio/staging

If you follow that link you should see a screen presenting buttons to click to get instructions for installing Debian/Rpm packages. Click on the appropriate link for instructions, and those should work for Ubuntu 16.04, 18.04, or Centos7. What to expect when following the link to https://packagecloud.io/fdio/release is in the image below: Packagecloud repo install

If you wish to install the merge-by-merge packages for the vpp master branch or the vpp stable/YYMM branches, the instructions are the same but use instead:

Install Packages


Once you have installed the repo:

sudo apt-get update sudo apt-get install vpp

  • Optional Debs
sudo apt-get install vpp-plugins vpp-dbg vpp-dev vpp-api-java vpp-api-python vpp-api-lua
  • Install all VPP packages
sudo apt-get install vpp*

Note: vpp-plugins contains the dpdk-plugin needed to use dpdk drivers for hardware interfaces.

  • Uninstalling Debs
sudo apt-get remove --autoremove --purge vpp*


Note: Circa 19.04-rc0 some dependencies were introduced for Centos7 packages are required to install VPP:

--> Finished Dependency Resolution
Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904)
           Requires: libmbedtls.so.10()(64bit)
Error: Package: vpp-devel-19.04-rc1~b4.x86_64 (fdio_1904)
           Requires: /usr/bin/python3
Error: Package: vpp-19.04-rc1~b4.x86_64 (fdio_1904)
           Requires: /usr/bin/python3
Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904)
           Requires: libmbedx509.so.0()(64bit)
Error: Package: vpp-plugins-19.04-rc1~b4.x86_64 (fdio_1904)
           Requires: libmbedcrypto.so.2()(64bit)

Installing the following packages on Centos7 resolves these dependency issues:

sudo yum install epel-release mbedtls python36

Once you have installed the repo:

sudo yum install vpp
  • Optional RPMs
sudo yum install vpp-plugins vpp-devel vpp-api-python vpp-api-lua vpp-api-java
  • Install all vpp packages
sudo yum install vpp*

Note: vpp-plugins contains the dpdk-plugin needed to use dpdk drivers for hardware interfaces.

  • Start VPP
sudo systemctl restart vpp

Uninstalling VPP RPMs

sudo yum autoremove vpp*


Blog-post: https://www.suse.com/communities/blog/vector-packet-processing-vpp-opensuse/

Install from official repositories

openSUSE Tumbleweed (rolling release)

sudo zypper install vpp vpp-plugins

openSUSE Leap 42.3

sudo zypper addrepo --name network https://download.opensuse.org/repositories/network/openSUSE_Leap_42.3/network.repo
sudo zypper install vpp vpp-plugins

Install from FD.io repositories

If the version of VPP you require has not yet made it in to the official repository you can elect to use the FD.io release repository.

openSUSE Leap 42.3

This repository is available since VPP 18.04.

sudo zypper addrepo --type rpm-md --name "FD.io release" https://nexus.fd.io/content/repositories/fd.io.osleap423/ fdio-leap423
sudo zypper install vpp vpp-plugins

openSUSE Leap 15

This repository is available since VPP 18.10.

If you are interested in cutting-edge master branch then:

sudo curl -s https://packagecloud.io/install/repositories/fdio/master/script.rpm.sh | sudo bash
sudo zypper install vpp vpp-plugins

If instead you are looking for a stable release, the latest and greatest available is 18.10

sudo curl -s https://packagecloud.io/install/repositories/fdio/1810/script.rpm.sh | sudo bash
sudo zypper install vpp vpp-plugins


openSUSE Tumbleweed (rolling release)

sudo zypper remove -u vpp vpp-plugins

openSUSE Leap 42.3

sudo zypper remove -u vpp vpp-plugins

Optionally also remove the repository:

sudo zypper removerepo network


sudo zypper removerepo fdio-leap423

Arch Linux

Available in the Arch User Repository (AUR): https://aur.archlinux.org/packages/vpp/

(Currently the bin packages do not work).

Getting jvpp jar

Directly downloading jvpp.jar

vpp provides java bindings which can be downloaded

Getting jvpp via maven

Add the following to the repositories section in your ~/.m2/settings.xml to pick up the fd.io maven repo:


More information on setting up maven repositories in settings.xml.

Then you can get jvpp by putting in the dependencies section of your pom.xml file:


More information on maven dependency managment

Old Nexus Apt/Yum repo instructions

If you wish to access the old Nexus Apt/Yum repo instructions there are available here.