On Fri, Dec 15, 2017 at 04:33:25PM +0530, Anoob Joseph wrote:
> Hi Nelio,
>
>
> On 12/15/2017 03:09 PM, Nelio Laranjeiro wrote:
> > Hi Anoob,
> >
> > On Fri, Dec 15, 2017 at 08:43:16AM +, Anoob Joseph wrote:
> > > Adding support for inline protocol processing
> > >
> > > In ingress side, ap
Hi Akhil,
On 12/15/2017 03:34 PM, Akhil Goyal wrote:
On 12/15/2017 2:13 PM, Anoob Joseph wrote:
Adding support for inline protocol processing
In ingress side, application will receive regular IP packets, without
any IPsec related info. Application will do a selector check (SP-SA
check) by mak
Hi Nelio,
On 12/15/2017 03:09 PM, Nelio Laranjeiro wrote:
Hi Anoob,
On Fri, Dec 15, 2017 at 08:43:16AM +, Anoob Joseph wrote:
Adding support for inline protocol processing
In ingress side, application will receive regular IP packets, without
any IPsec related info. Application will do a
On 12/15/2017 2:13 PM, Anoob Joseph wrote:
Adding support for inline protocol processing
In ingress side, application will receive regular IP packets, without
any IPsec related info. Application will do a selector check (SP-SA
check) by making use of the metadata from the packet. The
device-spec
Hi Anoob,
On Fri, Dec 15, 2017 at 08:43:16AM +, Anoob Joseph wrote:
> Adding support for inline protocol processing
>
> In ingress side, application will receive regular IP packets, without
> any IPsec related info. Application will do a selector check (SP-SA
> check) by making use of the met
Adding support for inline protocol processing
In ingress side, application will receive regular IP packets, without
any IPsec related info. Application will do a selector check (SP-SA
check) by making use of the metadata from the packet. The
device-specific metadata in mbuf would aid in determing
6 matches
Mail list logo
