<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<div><br>
</div>
<div>I was rewrite this feature as plugin using your recommendations.<br>
</div>
<div><br>
</div>
<div>Info about plugin:<br>
</div>
<div><br>
</div>
<div>After the last retransmit has been sent and the peer is considered dead ( plugin hooks ALERT_RETRANSMIT_SEND_TIMEOUT alert ), plugin sends an email with notification, which contains a name and an ip address of the dead peer, or( and ) executes external
command with two arguments: dead peer name and ip address. System administrators may find it useful for configuring email alerts and customizing other actions.<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>> For now,</div>
<div>> strongSwan supports some dpd actions such as 'clear', 'hold' and</div>
<div>> 'restart'. The patch implements new dpdaction named 'script'. It means</div>
<div>> that if no activity is detected, strongSwan executes external command</div>
<div>> with the dead peer passed as the argument for the command.</div>
<div><br>
</div>
<div>>> I don't agree with this approach. The actions are things to do with a</div>
<div>>> particular CHILD_SA/policy not unrelated things like calling a script to</div>
<div>>> email notifications. Instead, I propose you write a plugin that hooks</div>
<div>>> the ALERT_RETRANSMIT_SEND_TIMEOUT alert to get notified after the last</div>
<div>>> retransmit has been sent and the peer is considered dead. The plugin is</div>
<div>>> then free to do whatever it likes (e.g. calling a script).</div>
<div><br>
</div>
<div>>> Regards,</div>
<div>>> Tobias<br>
</div>
<div><br>
</div>
<div><br>
</div>
<p><br>
</p>
</body>
</html>