You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the implementation here. It seems we only support using the legacy strongSwan service unit with ipsec. But now the new version of strongSwan already uses swanctl to make configs and the IKE daemon that it's using is charon-systemd, not charon for the old version.
I wonder if OVS will do a migration for this. If this is not planned, can someone on the OVS side shed some lights on the outline of making such changes?
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
Based on the implementation here. It seems we only support using the legacy strongSwan service unit with
ipsec
. But now the new version of strongSwan already usesswanctl
to make configs and the IKE daemon that it's using ischaron-systemd
, notcharon
for the old version.I wonder if OVS will do a
migration
for this. If this is not planned, can someone on the OVS side shed some lights on the outline of making such changes?Thanks.
The text was updated successfully, but these errors were encountered: