Hi Alexandre,
> When running strongswan with the 3.2 kernel here is what i find in the logs:
>
> Feb 8 16:56:11 shire charon: 16[KNL] unable to add policy 172.17.2.0/24
> === 172.20.0.0/23 out
> Feb 8 16:56:11 shire charon: 16[KNL] unable to add policy 172.20.0.0/23
> === 172.17.2.0/24 in
> F
Here are some additionnal informations:
When running strongswan with the 3.2 kernel here is what i find in the logs:
Feb 8 16:56:11 shire charon: 16[KNL] unable to add policy 172.17.2.0/24
=== 172.20.0.0/23 out
Feb 8 16:56:11 shire charon: 16[KNL] unable to add policy 172.20.0.0/23
=== 172.17
Hi,
I had a working strongswan setup (4.4.1 from debian repository).
Recently I had to upgrade the kernel version of the server because of a
tiers software.
Since this upgrade tunnels just don't work that good and randomly fail
to keep up.
Is there anything I have to do (like recomplie strongsw
