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 speci
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
On Wed, Jul 20, 2016 at 6:13 AM, Tobias Brunner
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"
> >
