From 00faafed96d86a970bf566c79f1bfd304630ccaa Mon Sep 17 00:00:00 2001 From: zdc Date: Fri, 29 Aug 2025 19:53:13 +0300 Subject: VPP: Add comprehensive VPP documentation 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". --- docs/vpp/limitations.rst | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs/vpp/limitations.rst (limited to 'docs/vpp/limitations.rst') diff --git a/docs/vpp/limitations.rst b/docs/vpp/limitations.rst new file mode 100644 index 00000000..4c8910de --- /dev/null +++ b/docs/vpp/limitations.rst @@ -0,0 +1,33 @@ +: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. \ No newline at end of file -- cgit v1.2.3