On Wed, Jul 20, 2016 at 6:13 AM, Tobias Brunner <[email protected]> wrote: > > Hi Stig, > > > 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. > > Really? I don't think that ever was the case (at least not for IKEv2).
Previously we were mainly using ikev1 so maybe it's a pluto vs charon thing? Now that we are using charon I guess I have to re-work the way I handle changes (or get out the big hammer and "ipsec restart" ;-). Thanks for the quick answer. stig
_______________________________________________ Users mailing list [email protected] https://lists.strongswan.org/mailman/listinfo/users
