<font size=2 face="sans-serif">Hello list,</font>
<br>
<br><font size=2 face="sans-serif">I have to communicate to a cisco peer
that seems to disagree on lifetimes - it sends informational payload IPSEC_RESPONDER_LIFETIME
and sometimes just deletes SAs and then ignores any further attempts to
reestablish, resulting in a stale ISAKMP. That means I have to --down and
--up the connection to force a new Phase 1. </font>
<br>
<br><font size=2 face="sans-serif">I'm suspecting that thie IPSEC_RESPONDER_LIFETIME
might contain information that brings me closer to getting this connection
stable - unfortunately I cannot do anything with the payload:</font>
<br>
<br><font size=2 face="sans-serif">May 20 12:06:40 millhouse pluto[1584]:
| ISAKMP Notification Payload</font>
<br><font size=2 face="sans-serif">May 20 12:06:40 millhouse pluto[1584]:
| 00 00 00 1c 00 00 00 01 03 04 60 00</font>
<br>
<br><font size=2 face="sans-serif">How do I interpret those values? Or
do I have to enable debug logging to see what Lifetime the Cisco sends?</font>
<br>
<br><font size=2 face="sans-serif">And in a related question: My peer seems
to have enabled some sort of inactivity (or idle) timeout. Does LibreSWAN
have a similar feature? Or will auto=ondemand suffice once the SAs have
timed out?</font>
<br>
<br><font size=2 face="sans-serif">Best Regards</font>
<br><font size=2 face="sans-serif"> Heiko Helmle</font>