mirror of
https://github.com/vyos/vyos-documentation.git
synced 2025-10-26 01:31:44 +02:00
00faafed96
This commit introduces extensive documentation for VyOS VPP (Vector Packet Processing) Dataplane interfaces and features, including examples. Features documented: * VPP integration description, base requirements and limitations * VPP dataplane core settings * Features enabled in the dataplane: ACL, IPsec, NAT, sFlow * VPP interface types: bonding, bridge, GRE, IPIP, kernel, loopback, VXLAN, XConnect Note: This is an initial documentation version that will require ongoing improvements based on user feedback and questions, real-world deployment testing and validation, additional use cases and configuration scenarios discovered in production. Therefore, all pages are marked as "need improvement".
33 lines
1.2 KiB
ReStructuredText
33 lines
1.2 KiB
ReStructuredText
:lastproofread: 2025-09-04
|
|
|
|
.. _vpp_limitations:
|
|
|
|
.. include:: /_include/need_improvement.txt
|
|
|
|
#########################
|
|
VPP Dataplane Limitations
|
|
#########################
|
|
|
|
|
|
While VPP Dataplane offers significant performance advantages, there are some limitations and considerations to be aware of.
|
|
|
|
* **Feature Parity**
|
|
|
|
Not all features available in the Linux kernel dataplane are supported in VPP. Some networking features, specific protocols, or services may not be available.
|
|
|
|
VPP supports various interface types that have parity with kernel, but their capabilities may differ.
|
|
|
|
* **NIC and Drivers Compatibility**
|
|
|
|
Some NICs may work with DPDK drivers but not with XDP, or vice versa.
|
|
|
|
* **Data Path Limitations**
|
|
|
|
If a feature exists only in kernel dataplane, traffic using that feature will not be able to traverse VPP interfaces. Examples of such features are:
|
|
|
|
- Firewall
|
|
- QoS
|
|
|
|
When traffic uses pure VPP path, it simply never reaches the kernel where such features are implemented. Therefore, you need to carefully plan how traffic flows through VyOS router to ensure that it can reach expected features.
|
|
|
|
VPP has native replacements for some of these features, for example VPP native ACLs can satisfy basic firewalling needs. |