Dear Joerg,

On Tuesday 25 January 2005 11:23, Joerg Morbitzer wrote:
> I am running Debian testing on my main vpn gateway using openswan
> 2.2.0, the same setup is on all of my road-warriors.
> Yesterday one road-warrior was upgraded to Debian unstable with
> openswan 2.3.0, since then the openswan on my main vpn gateway
> crashes when this road-warrior is trying to establish the connection
> showing these lines in /var/log/syslog:
>
> Jan 25 10:52:57 darkstar ipsec__plutorun: /usr/lib/ipsec/_plutorun: line 1:
>  4974 Segmentation fault      /usr/lib/ipsec/pluto --nofork --secretsfile
> /etc/ipsec.secrets --ipsecdir /etc /ipsec.d --debug-none --uniqueids
> Jan 25 10:52:57 darkstar ipsec__plutorun: !pluto failure!:  exited with
> error status 139 (signal 11)
>
> I couldn't find a core file unfortunately.
>
> We manually downgraded to openswan 2.2.0 and everything is ok again.
I have also encountered this issue and am trying to track it down.

with best regards,
Rene


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to