blob: da9bff036bf59e14e2b055b0ae1565a8d77e1d8f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
:lastproofread: 2026-03-13
.. _vpp_config_interfaces_index:
.. include:: /_include/need_improvement.txt
############################
VPP Interfaces Configuration
############################
.. toctree::
:maxdepth: 1
:includehidden:
bonding
bridge
gre
ipip
loopback
vxlan
xconnect
VyOS utilizes VPP (Vector Packet Processor) to provide high-performance data
plane processing. While physical interfaces are typically managed through the
Linux kernel using ``linux-cp`` (Linux Control Plane) integration, VyOS also
supports creating dedicated VPP interfaces for enhanced flexibility and
performance.
Why VPP Interfaces?
-------------------
VPP interfaces offer several advantages:
* **Total Isolation**: VPP interfaces operate entirely within the VPP data
plane, providing isolation from the Linux kernel when needed.
* **Advanced Features**: Access to VPP-specific functionality not available
in standard Linux interfaces.
* **Flexible Deployment**: Some interface types are only available as VPP
interfaces or may not be supported by the kernel.
* **Specific scenarios**: Not all use cases require integration with the
Linux Kernel.
Integration with Kernel
^^^^^^^^^^^^^^^^^^^^^^^
VyOS provides seamless integration between VPP and kernel networking.
This allows you to leverage the strengths of both approaches:
create interfaces inside VPP, and access them from the Linux kernel and other
services.
|
