[Openswan Users] Tunnels established, but reset in seconds

[Charlie Hedlin]

I have searched the archive, and I must be missing something, but I 
can't seem to figure out where to go.  I worked with FreeSWAN very 
successfully about 4 years ago, interoperating with Cisco.

Now I am tyring to bring up a VPN connection to a Draytek Vigor router. 
I am running Debian/testing with Openswan 2.2.0 installed using apt and 
dpkg.  I am using the native IPSec kernel drivers (quite different from 
FreeSWAN on a 2.0 kernel).

Running tcpdump and looking through the logs I can see it completing 
phase I and starting phase II.  It restarts every few seconds. 

Here is the output of the commands to bring up the connection, and then 
a Status shortly thereafter.  I have barf output if it will help, but I 
don't want to flood the list with that long of a message.

gateway:/var/log# /etc/init.d/ipsec stop
ipsec_setup: Stopping Openswan IPsec...
gateway:/var/log# /etc/init.d/ipsec start
ipsec_setup: Starting Openswan IPsec U2.2.0/K2.6.8-1-686-smp...
gateway:/var/log# ipsec auto --up HongKong
104 "HongKong" #1: STATE_MAIN_I1: initiate
106 "HongKong" #1: STATE_MAIN_I2: sent MI2, expecting MR2
108 "HongKong" #1: STATE_MAIN_I3: sent MI3, expecting MR3
010 "HongKong" #1: STATE_MAIN_I3: retransmission; will wait 20s for response
004 "HongKong" #1: STATE_MAIN_I4: ISAKMP SA established
112 "HongKong" #2: STATE_QUICK_I1: initiate
004 "HongKong" #2: STATE_QUICK_I2: sent QI2, IPsec SA established 
{ESP=>0x7fffff4d <0xff1a3f83}
gateway:/var/log# ipsec auto --status
000 interface lo/lo ::1
000 interface lo/lo 127.0.0.1
000 interface eth0/eth0 10.2.0.15
000 interface eth1/eth1 64.47.64.147
000 %myid = (none)
000 debug 
raw+crypt+parsing+emitting+control+lifecycle+klips+dns+oppo+controlmore+pfkey+nattraversal+x509
000
000 algorithm ESP encrypt: id=2, name=ESP_DES, ivlen=8, keysizemin=64, 
keysizemax=64
000 algorithm ESP encrypt: id=3, name=ESP_3DES, ivlen=8, keysizemin=192, 
keysizemax=192
000 algorithm ESP encrypt: id=7, name=ESP_BLOWFISH, ivlen=8, 
keysizemin=40, keysizemax=448
000 algorithm ESP encrypt: id=11, name=ESP_NULL, ivlen=0, keysizemin=0, 
keysizemax=0
000 algorithm ESP encrypt: id=12, name=ESP_AES, ivlen=8, keysizemin=128, 
keysizemax=256
000 algorithm ESP encrypt: id=252, name=ESP_SERPENT, ivlen=8, 
keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=253, name=ESP_TWOFISH, ivlen=8, 
keysizemin=128, keysizemax=256
000 algorithm ESP auth attr: id=1, name=AUTH_ALGORITHM_HMAC_MD5, 
keysizemin=128, keysizemax=128
000 algorithm ESP auth attr: id=2, name=AUTH_ALGORITHM_HMAC_SHA1, 
keysizemin=160, keysizemax=160
000 algorithm ESP auth attr: id=5, name=AUTH_ALGORITHM_HMAC_SHA2_256, 
keysizemin=256, keysizemax=256
000 algorithm ESP auth attr: id=251, name=(null), keysizemin=0, keysizemax=0
000
000 algorithm IKE encrypt: id=7, name=OAKLEY_AES_CBC, blocksize=16, 
keydeflen=128
000 algorithm IKE encrypt: id=5, name=OAKLEY_3DES_CBC, blocksize=8, 
keydeflen=192
000 algorithm IKE hash: id=2, name=OAKLEY_SHA, hashsize=20
000 algorithm IKE hash: id=1, name=OAKLEY_MD5, hashsize=16
000 algorithm IKE dh group: id=2, name=OAKLEY_GROUP_MODP1024, bits=1024
000 algorithm IKE dh group: id=5, name=OAKLEY_GROUP_MODP1536, bits=1536
000 algorithm IKE dh group: id=14, name=OAKLEY_GROUP_MODP2048, bits=2048
000 algorithm IKE dh group: id=15, name=OAKLEY_GROUP_MODP3072, bits=3072
000 algorithm IKE dh group: id=16, name=OAKLEY_GROUP_MODP4096, bits=4096
000 algorithm IKE dh group: id=17, name=OAKLEY_GROUP_MODP6144, bits=6144
000 algorithm IKE dh group: id=18, name=OAKLEY_GROUP_MODP8192, bits=8192
000
000 stats db_ops.c: {curr_cnt, total_cnt, maxsz} :context={0,4,36} 
trans={0,4,336} attrs={0,4,224}
000
000 "HongKong": 
10.2.0.0/16===64.47.64.147---64.47.64.145...203.105.59.161===192.168.1.0/24; 
erouted; eroute owner: #2
000 "HongKong":   ike_life: 3600s; ipsec_life: 28800s; rekey_margin: 
540s; rekey_fuzz: 100%; keyingtries: 0
000 "HongKong":   policy: PSK+ENCRYPT+TUNNEL+UP; prio: 16,24; interface: 
eth1;
000 "HongKong":   newest ISAKMP SA: #0; newest IPsec SA: #2;
000 "HongKong":   IKE algorithms wanted: 5_000-1-5, 5_000-1-2, 
5_000-2-5, 5_000-2-2, flags=-strict
000 "HongKong":   IKE algorithms found:  5_192-1_128-5, 5_192-1_128-2, 
5_192-2_160-5, 5_192-2_160-2,
000 "HongKong":   ESP algorithms wanted: 3_000-1, 3_000-2, flags=-strict
000 "HongKong":   ESP algorithms loaded: 3_000-1, 3_000-2, flags=-strict
000 "HongKong":   ESP algorithm newest: 3DES_0-HMAC_MD5; pfsgroup=<N/A>
000
000 #2: "HongKong" STATE_QUICK_I2 (sent QI2, IPsec SA established); 
EVENT_SA_REPLACE in 3s; newest IPSEC; eroute owner
000 #2: "HongKong" esp.7fffff4d at 203.105.59.161 esp.ff1a3f83 at 64.47.64.147 
tun.0 at 203.105.59.161 tun.0 at 64.47.64.147
000