<html><head></head><body>Hi,<br><br>Configure your own side with lower reauth and rekey times than the other peer.<br>Currently the other peer tries to reauth which fails because you're using the insecure aggressive mode. strongSwan by default rejects other peers' authentication requests if they're using aggressive mode.<br>A reauthentication is basically creating a new IKE_SA from scratch, so that behavior applies.<br><br>Just configure your client with lower rekey and reauth times. That's simpler than globally enabling aggressive mode.<br><br>Kind regards<br><br>Noel<br><br><div class="gmail_quote">Am October 16, 2020 11:09:29 AM UTC schrieb Chris Smith <space.dandy@icloud.com>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hi,<br><br>[re-sending with trimmed down charon.log to fit mailing list size limits.]<br><br>I have a VPN connection which is generally stable, but occasionally (2-3 times per day) will drop out for a short period after what seems to be some disagreement between client and server. The logs attached show an example of this, where the connection fails around 18:24:35 and is restored around a minute later.<br><br>I’m using strongSwan 5.7.2 on the client. I have no information or control over what is running on the server.<br><br>I’d be grateful for any clues as to exactly what is happening and how to correct it.<br><br>Regards,<br>Chris<br>—<br>Chris Smith <space.dandy@icloud.com><br><br></pre></blockquote></div><br>-- <br>Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</body></html>