ror0 = ETHERNET_ERROR_L3_MAC_MISMATCH;
Regards,
John
From: Damjan Marion
Sent: Friday, March 22, 2019 3:41 AM
To: Ni, Hongjun
Cc: John Lo (loj) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Status of PPPoE Plugin
On 22 Mar 2019, at 07:34, Ni, Hongjun
mailto:hongjun...@intel.com>>
Thanks Damjan. Will look into it and find some way to resolve it.
Thanks,
Hongjun
From: Damjan Marion [mailto:dmar...@me.com]
Sent: Friday, March 22, 2019 3:41 PM
To: Ni, Hongjun
Cc: l...@cisco.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Status of PPPoE Plugin
On 22 Mar 2019, at 07:34
>
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of John Lo
> (loj) via Lists.Fd.Io
> Sent: Thursday, March 21, 2019 11:34 PM
> To: dmar...@me.com; Ni, Hongjun
> Cc: vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] Status of PPPoE Plugin
>
> Thanks
:34 PM
To: dmar...@me.com; Ni, Hongjun
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Status of PPPoE Plugin
Thanks for citing the PPPoE RFC 2516, Damjan. The RFC goes on to describe how
to resolve the MAC address for PPPoE sessions in Section 5 in discovery stage.
As such, there is really
was MAC address
resolution for PPPoE sessions. -John
From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via
Lists.Fd.Io
Sent: Thursday, March 21, 2019 11:08 AM
To: Ni, Hongjun
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Status of PPPoE Plugin
> On 21 Mar 2019, at 06:20, Ni, Hong
pp-dev@lists.fd.io] On Behalf Of Raj
> Sent: Wednesday, March 20, 2019 9:48 PM
> To: vpp-dev
> Cc: alp.ars...@xflowresearch.com; Ni, Hongjun
> Subject: Re: [vpp-dev] Status of PPPoE Plugin
>
> I commented out the offending parts and now PPPoE is working fine.
>
> diff --git
: alp.ars...@xflowresearch.com; Ni, Hongjun
Subject: Re: [vpp-dev] Status of PPPoE Plugin
I commented out the offending parts and now PPPoE is working fine.
diff --git a/src/vnet/ethernet/node.c b/src/vnet/ethernet/node.c index
53d5b4eb0..7c5f673e0 100755
--- a/src/vnet/ethernet/node.c
+++ b/src/vnet
I commented out the offending parts and now PPPoE is working fine.
diff --git a/src/vnet/ethernet/node.c b/src/vnet/ethernet/node.c
index 53d5b4eb0..7c5f673e0 100755
--- a/src/vnet/ethernet/node.c
+++ b/src/vnet/ethernet/node.c
@@ -429,14 +429,14 @@ ethernet_input_inline (vlib_main_t * vm,
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
On Thu, Dec 20, 2018 at 6:17 AM Ni, Hongjun 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
t; Thank you for your great help!
> -Original Message-
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Raj
> Sent: Tuesday, December 18, 2018 8:11 PM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Status of PPPoE Plugin
>
> Hello all,
>
> I
lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Raj
> > Sent: Tuesday, December 18, 2018 8:11 PM
> > To: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] Status of PPPoE Plugin
> >
> > Hello all,
> >
> > I am trying out PPPoE with VPP and while seaching for its
Hongjun
>
> -Original Message-
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Raj
> Sent: Tuesday, December 18, 2018 8:11 PM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] Status of PPPoE Plugin
>
> Hello all,
>
> I am trying out PPP
PM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Status of PPPoE Plugin
Hello all,
I am trying out PPPoE with VPP and while seaching for its configuration I found
the following thread
https://lists.fd.io/g/vpp-dev/message/10844 which kind of suggests that the
currently PPPoE is broken
Hello all,
I am trying out PPPoE with VPP and while seaching for its
configuration I found the following thread
https://lists.fd.io/g/vpp-dev/message/10844 which kind of suggests
that the currently PPPoE is broken and that the code must be moved to
tapv2.
The problem people get is that packets
15 matches
Mail list logo
