[Openswan Users] Tunnel fails to start, but nothing logged....

[Matthew Claridge]

Hi,

I'm setting up a vpn tunnel to one of our customers' Cisco Pix 
firewalls, from a Fedora Core5 system, using OpenSwan-2.4.4-1.1.2.1

The tunnel is failing to start, but nothing useful is logged:

     Jul 24 00:12:44 vpn1 ipsec_setup: KLIPS ipsec0 on eth0 
62.189.139.60/255.255.255.0 broadcast 62.189.139.255
     Jul 24 00:12:44 vpn1 ipsec_setup: ...Openswan IPsec started
     Jul 24 00:12:47 vpn1 ipsec__plutorun: 104 "amextunnel" #1: 
STATE_MAIN_I1: initiate
     Jul 24 00:12:47 vpn1 ipsec__plutorun: ...could not start conn 
"amextunnel"

This is my ipsec.conf:

config setup
        interfaces=%defaultroute
        klipsdebug=all
        plutodebug=all
        nat_traversal=yes

conn amextunnel
        type=           tunnel
        left=           62.189.139.60
        leftnexthop=    62.189.139.5
        leftsubnet=     192.168.5.0/24
        right=          89.234.17.132
        rightnexthop=
        rightsubnet=    192.168.201.0/24
        esp=            3des-sha1-96
        keyexchange=    ike
        pfs=            no
        auto=           start


The log entries and results are identical whether I use OE or not.

Anyone have any ideas what might be going on, where to start looking or 
how to get more information out of it?

Thanks in advance,
Matt