Hi Ole, Yes, one TAP interface is only needed.
Memif is a good way to redirect CP traffic. But reworking control plane code is required because the open source CP project is using kernel's socket. Currently, we only use TAP port to minimize the integration effort. Thanks, Hongjun -----Original Message----- From: Ole Troan [mailto:otr...@employees.org] Sent: Monday, June 26, 2017 4:26 PM To: Ni, Hongjun <hongjun...@intel.com> Cc: Ed Warnicke <hagb...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] PPPOE Hi Hongjun, > PPPoE plugin will support any kind of control plan projects. > > Currently, we plan to test slow path code using below open source control > plan project: > https://github.com/wfnex/openbras > > We will create a tap port hooked to the kernel -> OpenBRAS The slow > path graph node will forward all non PPPoE session stage traffic to control > plane via TAP port. You only need one TAP interface, even if you have PPPoE enabled on more than one interface right? Alternatively we have the Punt UDS socket for control traffic (which has additional meta-data like RX/TX ifindex) or Damjan is working on using the memif interface for control plane traffic too. Cheers, Ole _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
