> -Original Message-
> From: Neale Ranns (nranns)
> Sent: Wednesday, October 12, 2016 10:26 AM
> To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
> ; Zdenko Olsovsky -X (zolsovsk - PANTHEON
> TECHNOLOGIES at Cisco) ; vpp-dev@lists.fd.io
> Cc: csit-...@lists.fd.io
> Subject: R
On 12/10/16 09:16, Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
wrote:
IPSec tunnel interface is associated with SA, it is similar to ipsec-gre
interface. Functionality is equivalent to IPSec as in/out feature it
encapsulate/decapsulate packet to ESP. But it doesn't use standar
Comments inline
Regards,
Matus
> -Original Message-
> From: Neale Ranns (nranns)
> Sent: Wednesday, October 12, 2016 9:33 AM
> To: Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
> ; Zdenko Olsovsky -X (zolsovsk - PANTHEON
> TECHNOLOGIES at Cisco) ; vpp-dev@lists.fd.io
> Cc: c
Hi Matus,
On 12/10/16 06:46, Matus Fabian -X (matfabia - PANTHEON TECHNOLOGIES at Cisco)
wrote:
Hi Neale,
IPSec interface is tunnel interface created by IKEv2 code when child SA is
successfully established.
is it similar to the ipsec-gre interface we were discussing earlier? i.e. it is
func
Hi Neale,
IPSec interface is tunnel interface created by IKEv2 code when child SA is
successfully established.
You can't set IP on it because there is missing
"ip4_sw_interface_enable_disable" when interface is created, I will fix it.
Regards,
Matus
> -Original Message-
> From: csit-de
