Call for Contributions

This section needs improvements, examples and explanations.

Please take a look at the Contributing Guide for our Write Documentation.

VPP Interfaces Configuration

• VPP Bonding Configuration
• VPP Bridge Configuration
• VPP GRE Configuration
• VPP IPIP Configuration
• VPP Kernel Interfaces Configuration
• VPP Loopback Interface Configuration
• VPP VXLAN Configuration
• VPP XConnect Configuration

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

However, if needed, VyOS provides seamless integration between VPP and kernel networking. For detailed information about kernel interface integration, see VPP Kernel Interfaces Configuration.

This allows you to leverage the strengths of both approaches - create interfaces inside VPP, but still have them accessible from the Linux kernel and other services side.