<html>
<body>
At 01:23 AM 12/3/2007 -0500, you wrote:<br>
>At 04:39 PM 12/2/2007 -0500, Michael Richardson wrote:<br>
>> Also look at "ipsec spi" output.<br>
><br>
>Adding this command to the 60 second loop causes<br>
>the OpenSwan and the transfer to hose up in a matter<br>
>of an hour or two, so I have removed it. Will run<br>
>the command after the lock-up that results from<br>
>7GB of data transfer.<br>
><br>
>Tried stop/starting OpenSwan, but it did not restore<br>
>everything, so had to reboot the router. Seems some<br>
>kernel corruption happens in this case.<br><br>
Not so sure about this now. Restarted transfer blew up within <br>
an hour after restarting at 3:00am. Now I'm wondering if the <br>
Cisco VPN firewall was hosed by the transfers. Looks like the <br>
remote side was reset at 9:00am, eliminating the persistant <br>
packet loss that had appeared coincident with the short-interval <br>
failures.<br><br>
Is this something anyone has encountered before?<br><br>
<br>
<img src="cid:6.2.5.6.2.20071203102707.01cac2b0@binnacle.cx.0" width=960 height=725 alt="Emacs!">
</body>
</html>