Initial checkin - renamed the files to avoid clashing with 'lcp' and 'linux-cp' plugin
This commit is contained in:
25
FEATURE.yaml
Normal file
25
FEATURE.yaml
Normal file
@ -0,0 +1,25 @@
|
||||
---
|
||||
name: Linux Control Plane (integration)
|
||||
maintainer: Neale Ranns <neale@grahpiant.com>
|
||||
|
||||
description: |-
|
||||
This plugin provides the beginnings of an integration with the
|
||||
Linux network stack.
|
||||
The plugin provides the capability to 'mirror' VPP interfaces in
|
||||
the Linux kernel. This means that for any interface in VPP the user
|
||||
can create a corresponding TAP or TUN device in the Linux kernel
|
||||
and have VPP plumb them together.
|
||||
The plumbing mechanics is different in each direction.
|
||||
In the RX direction, all packets received on a given VPP interface
|
||||
that are punted (i.e. are not dropped or forwarded) are transmitted
|
||||
on its mirror interface (this includes for example ARP, ND etc,
|
||||
so the recommendation is to disable ARP, ND, ping plugin).
|
||||
In the TX direction, packets received by VPP an the mirror Tap/Tun
|
||||
are cross-connected to the VPP interfaces. For IP packets, IP output
|
||||
features are applied.
|
||||
This is the beginnings of integration, because there needs to be
|
||||
an external agent that will configure (and synchronize) the IP
|
||||
configuration of the paired interfaces.
|
||||
|
||||
state: experimental
|
||||
properties: [API, CLI, MULTITHREAD]
|
Reference in New Issue
Block a user