17.09.2020 04:16, Glen пишет:
CAUSES IDENTIFIED:
At some point in an update, the behavior of strongswan changed without warning. Strongswan started *ignoring* the /etc/ipsec.conf file completely. Digging into the documentation, I discovered that /etc/ipsec.conf was being deprecated by the Strongswan team in favor of /etc/swanctl/swanctl.conf.
HOWEVER, that change was *not* picked up on by yast2. Yast2 continues to pretend to configure VPNs, and appears to function properly; however, it writes an /etc/ipsec.conf file each time, which is ignored by Strongswan.
You should open bug report. Such changes are not acceptable in stable releases. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org