Adds the link to OpenBras we are using: https://github.com/wfnex/openbras
Correct below type error: //Configure CP path and DP session in CLI: vppctl create pppoe tap client-if-index 2 tap-if-index 1 vppctl create pppoe session client-ip 100.1.1.2 session-id 1 local-mac 68:05:ca:30:54:e8 client-mac 00:11:01:00:00:01 vppctl ip route add 100.1.1.2/24 via pppoe_session0 Thanks, Hongjun -----Original Message----- From: Ni, Hongjun Sent: Tuesday, July 18, 2017 10:35 AM To: Ni, Hongjun <hongjun...@intel.com>; Ole Troan <otr...@employees.org> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: RE: [vpp-dev] PPPOE Hi all, The initial PPPoE plugin code has been done and submitted for review. https://gerrit.fd.io/r/#/c/7407/ Add PPPoE Plugin Please feel free to review it and give some comments. We have successfully integrated VPP, PPPoE plugin and OpenBRAS together and used IXIA PPPoE test suit to perform both functional and performance test. This plugin adds three graph nodes: 1) pppoe-input for PPPoE decapsulation 2) pppoe-encap for PPPoE encapsulation 3) pppoe-tap-dispatch for steering control plane packets between Subscribers and OpenBRAS. Below is the configuration to make PPPoE CP and DP work: vim /etc/vpp/startup.conf tuntap { enable ethernet name newtap } vppctl create pppoe tap client-if-index 2 tap-if-index 1 vppctl create pppoe session client-ip 100.1.1.2 session-id 1 local-mac 68:05:ca:30:54:e8 client-mac 00:11:01:00:00:01 vppctl ip route add 100.1.1.2/24 via pppoe_session0 Further optimization includes: 1. Forwarding rules among all available dataplane ports on subscriber side (Currently it only supports one interface). 2. Optimize away the "ip route" command which should be added automatically when creating PPPoE sessions. Thanks a lot, Hongjun -----Original Message----- From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Ni, Hongjun Sent: Monday, June 26, 2017 4:46 PM To: Ole Troan <otr...@employees.org> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] PPPOE 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 _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
