summaryrefslogtreecommitdiffstats
path: root/src/vnet/srv6
AgeCommit message (Expand)AuthorFilesLines
2018-07-12srv6: fix pointers in quad loopsFrancois Clad1-6/+6
2018-07-11avoid using thread local storage for thread indexDamjan Marion1-2/+2
2018-06-19Fixed bugs in SRv6 APIPablo Camarillo3-56/+216
2018-04-25Fix some build warnings about "Old Style VLA"Juraj Sloboda1-2/+7
2018-03-14srv6-plugins: fixing documentationFrancois Clad1-0/+7
2018-03-14srv6: minor CLI modificationsFrancois Clad4-15/+14
2018-02-27SRv6: API uses table-IDs not FIB indiciesNeale Ranns1-3/+3
2018-01-23VPPAPIGEN: vppapigen replacement in Python PLY.Ole Troan1-1/+1
2018-01-11api: remove transport specific code from handlersFlorin Coras1-9/+7
2018-01-09VPP-1120 SRv6 bug with SID list containing only one SID and no srhPablo Camarillo1-26/+64
2018-01-09api: refactor vlibmemoryFlorin Coras1-2/+2
2017-11-27SRv6 improvements to binary APIPablo Camarillo4-22/+84
2017-11-10add classify session action set-sr-policy-indexGabriel Ganne1-0/+24
2017-11-09BIERNeale Ranns1-1/+1
2017-10-09vppapigen: support per-file (major,minor,patch) version stampsDave Barach1-2/+6
2017-09-27Various fixes for issues found by Coverity (VPP-972)Chris Luke1-0/+10
2017-09-11FIB table add/delete APINeale Ranns2-4/+8
2017-08-22SRv6 testsKris Michielsen3-32/+201
2017-08-08L2 over MPLSNeale Ranns1-2/+2
2017-06-07VPP-872 and End.T function for SRv6Pablo Camarillo2-105/+101
2017-05-05First commit SR MPLSPablo Camarillo14-0/+8014
API test program | | @ref src/vlib | VPP application library | | @ref src/vlibapi | VPP API library | | @ref src/vlibmemory | VPP Memory management | | @ref src/vnet | VPP networking | | @ref src/vpp | VPP application | | @ref src/vpp-api | VPP application API bindings | | @ref src/vppinfra | VPP core library | | @ref src/vpp/api | Not-yet-relocated API bindings | | test | Unit tests and Python test harness | ## Getting started In general anyone interested in building, developing or running VPP should consult the [VPP wiki](https://wiki.fd.io/view/VPP) for more complete documentation. In particular, readers are recommended to take a look at [Pulling, Building, Running, Hacking, Pushing](https://wiki.fd.io/view/VPP/Pulling,_Building,_Run ning,_Hacking_and_Pushing_VPP_Code) which provides extensive step-by-step coverage of the topic. For the impatient, some salient information is distilled below. ### Quick-start: On an existing Linux host To install system dependencies, build VPP and then install it, simply run the build script. This should be performed a non-privileged user with `sudo` access from the project base directory: ./extras/vagrant/build.sh If you want a more fine-grained approach because you intend to do some development work, the `Makefile` in the root directory of the source tree provides several convenience shortcuts as `make` targets that may be of interest. To see the available targets run: make ### Quick-start: Vagrant The directory `extras/vagrant` contains a `VagrantFile` and supporting scripts to bootstrap a working VPP inside a Vagrant-managed Virtual Machine. This VM can then be used to test concepts with VPP or as a development platform to extend VPP. Some obvious caveats apply when using a VM for VPP since its performance will never match that of bare metal; if your work is timing or performance sensitive, consider using bare metal in addition or instead of the VM. For this to work you will need a working installation of Vagrant. Instructions for this can be found [on the Setting up Vagrant wiki page] (https://wiki.fd.io/view/DEV/Setting_Up_Vagrant). ## More information Several modules provide documentation, see @subpage user_doc for more end-user-oriented information. Also see @subpage dev_doc for developer notes. Visit the [VPP wiki](https://wiki.fd.io/view/VPP) for details on more advanced building strategies and other development notes. ## Test Framework There is PyDoc generated documentation available for the VPP test framework. See @ref test_framework_doc for details.