Hi Joy, kernel_ipsec_t just defines a standardized strongSwan interface, but the actual interface code is in the plugins. So if you have an IPsec ESP implementation of your own, e.g. a HW accelerator then you have to write a plugin of your own.
Best regards
Andreas
BTW - In the latest strongSwan releases libhydra doesn't exist any more.
The functionality has been moved back to libcharon.
On 15.11.2016 17:01, Joy Latten wrote:
> Hi Tobias,
>
> Thank you!
> So is it safe to conclude that without a plugin, libhydra does nothing?
> (I think you get return of "NOT_SUPPORTED".)
> And libhydra is required in order for charon/ike to manage SAs and SPs
> with kernel.
>
> Again, thanks!
>
> regards,
> Joy
>
> On 11/15/2016 01:53 AM, Tobias Brunner wrote:
>> Hi Joy,
>>
>>> Any new plugin for talking
>>> to the kernel would require a kernel_ipsec_t as well. Is this correct?
>>
>> Yes.
>>
>> Regards,
>> Tobias
>>
> _______________________________________________
> Users mailing list
> Users@lists.strongswan.org
> https://lists.strongswan.org/mailman/listinfo/users
>
--
======================================================================
Andreas Steffen andreas.stef...@strongswan.org
strongSwan - the Open Source VPN Solution! www.strongswan.org
Institute for Internet Technologies and Applications
University of Applied Sciences Rapperswil
CH-8640 Rapperswil (Switzerland)
===========================================================[ITA-HSR]==
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list Users@lists.strongswan.org https://lists.strongswan.org/mailman/listinfo/users
