Re: Can not start conn with FreeS/WAN U2.04/K2.2.0 (kernel 2.4.26) after Update from 1.96

From: Natanael Mignon (usenet_trashcan_nospam_at_bleeding.de)
Date: 07/12/05 

Date: Tue, 12 Jul 2005 11:47:39 +0200

on 12.07.2005 10:02 Natanael Mignon wrote:
> meanwhile. This means: FreeS/WAN 2.04 and kernel patches 2.2.0 on kernel
> 2.4.26 (because from 2.4.27 on the kernel has the backported ipsec stuff
Update.

Took freeswan from Debian/Testing meanwhile (depends on ipsec-tools and
openswan 2.2.0 - so we're talking about OpenS/WAN 2.2 now). The messages
and results are exactly the same as before.

Ethereal sniffing on the router between the two gateways shows full IKE
dialogues; Informational, MainMode and encrypted chat in QuickMode -
finalizing with a last Informational package with encrypted payload and
that's it. Nothing really of help to me. :-(

> -+-+-+-+<syslog>-+-+-+-+-
> Jul 12 08:44:29 lnx-fw2 ipsec_setup: KLIPS ipsec0 on eth1
> 212.86.147.194/255.255.255.252 broadcast 212.86.147.195
> Jul 12 08:44:29 lnx-fw2 ipsec_setup: ...FreeS/WAN IPsec started
> Jul 12 08:44:31 lnx-fw2 ipsec__plutorun: 104 "H1" #1: STATE_MAIN_I1:
> initiate
> Jul 12 08:44:31 lnx-fw2 ipsec__plutorun: ...could not start conn "H1"
> -+-+-+-+</syslog>-+-+-+-+-

Best regards 

-- 
  - Nat
Metal headquarters @ http://bleeding.4metal.net
Technology of the 4Metal.net : http://tech.4metal.net