Another approach that can be used is to send all PPP/PPPoE control packets encapsulated in NSH, and Control plane can process it and return the packets to VPP which will decapsulate the NSH headers and pass the packets on to PPPoE client.
Thanks and Regards, Raj On Mon, Mar 18, 2019 at 7:44 PM Raj via Lists.Fd.Io <rajlistuser=gmail....@lists.fd.io> wrote: > > On Thu, Dec 20, 2018 at 6:17 AM Ni, Hongjun <hongjun...@intel.com> wrote: > > > For the issue you mentioned, Alp Arslan in the To list will submit a patch > > to fix it. > > I can take a stab at this and prepare a patch to get PPPoE working > again in VPP. I understand that this error happens because VPP will > only allow packets whose destination MAC is the same as the interface > MAC or bcast/mcast MAC. How should I go about fixing this? Would > turning off off this check for TAP interface work? Any better way to > achieve this result? > > Thanks and Regards, > > Raj
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12588): https://lists.fd.io/g/vpp-dev/message/12588 Mute This Topic: https://lists.fd.io/mt/28791570/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
