>
> >
> > Ok, so to confirm:
> > Your only issue here is that patch is that we have to split ipsec-secgw
> > SADB into
> > two?
> >
> > No objections to other part:
> > - search for given SPI value across both SPDs (IPv4 and IPv6)
> > - for each positive result create a new SA.
> > So if we ha
>
> Ok, so to confirm:
> Your only issue here is that patch is that we have to split ipsec-secgw SADB
> into
> two?
>
> No objections to other part:
> - search for given SPI value across both SPDs (IPv4 and IPv6)
> - for each positive result create a new SA.
> So if we have same SPI in both IPv
> > > > Ipsec-secgw example application fails to initialize when using default
> > > > configuration file (ep0.cfg) in library mode (librte_ipsec enabled).
> > > >
> > > > The reason is that two of SP rules in ep0.cfg, one for IPv4 and one
> > > > for IPv6, are using the same SPI number. When SA
Hi Konstantin,
>
> Hi Akhil,
>
> > > Ipsec-secgw example application fails to initialize when using default
> > > configuration file (ep0.cfg) in library mode (librte_ipsec enabled).
> > >
> > > The reason is that two of SP rules in ep0.cfg, one for IPv4 and one
> > > for IPv6, are using the same
Hi Akhil,
> > Ipsec-secgw example application fails to initialize when using default
> > configuration file (ep0.cfg) in library mode (librte_ipsec enabled).
> >
> > The reason is that two of SP rules in ep0.cfg, one for IPv4 and one
> > for IPv6, are using the same SPI number. When SA rules are
Hi Mariusz,
> -Original Message-
> From: Mariusz Drost
> Sent: Tuesday, September 24, 2019 4:06 PM
> To: radu.nico...@intel.com; Akhil Goyal ;
> konstantin.anan...@intel.com
> Cc: dev@dpdk.org; Mariusz Drost ; Lukasz Bartosik
>
> Subject: [PATCH v2 1/2] examples/ipsec-secgw: fix SAD sel
On 9/24/2019 11:35 AM, Drost, MariuszX wrote:
Ipsec-secgw example application fails to initialize when using default
configuration file (ep0.cfg) in library mode (librte_ipsec enabled).
The reason is that two of SP rules in ep0.cfg, one for IPv4 and one
for IPv6, are using the same SPI number.
> Ipsec-secgw example application fails to initialize when using default
> configuration file (ep0.cfg) in library mode (librte_ipsec enabled).
>
> The reason is that two of SP rules in ep0.cfg, one for IPv4 and one
> for IPv6, are using the same SPI number. When SA rules are initialized,
> thei
8 matches
Mail list logo
