[strongSwan] ipsec update restarting affected tunnels

Stig Thormodsrud stig at ubnt.com
Wed Jul 20 00:56:31 CEST 2016

I've recently upgraded our strongswan from 4.5.2 to 5.2.2 and one of the
differences I noticed is with the older version I could regenerate
/etc/ipsec.conf and then do "ipsec rereadall" followed by "ipsec update"
and any tunnels that were affected would restart.  Now with 5.2.2 I see the
docs specifically say that "Currently established connections are not
affected by configuration changes".  I know I could use "ipsec down|up"
with the specific tunnel, but is there another command will has the same
behavior as the older version?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/users/attachments/20160719/698ab669/attachment.html>

More information about the Users mailing list