[Openswan Users] esp string error: enc_alg not found

Mon May 17 19:45:14 EDT 2010

I got a little more info as below when running "ipsec auto --status". it seems hang on Phase 2...

[root at fw1 ipsec.d]# ipsec auto --status
000 using kernel interface: netkey
000 interface lo/lo ::1
000 interface lo/lo 127.0.0.1
000 interface eth0/eth0 192.168.1.152
000 interface eth1.100/eth1.100 209.190.164.199
000 %myid = (none)
000 debug raw+crypt+parsing+emitting+control+lifecycle+klips+dns+oppo+controlmore+pfkey+nattraversal+x509
000
000 virtual_private (%priv):
000 - allowed 0 subnets:
000 - disallowed 0 subnets:
000 WARNING: Either virtual_private= was not specified, or there was a syntax
000          error in that line. 'left/rightsubnet=%priv' will not work!
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=14, name=ESP_AES_CCM_A, ivlen=8, keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=15, name=ESP_AES_CCM_B, ivlen=8, keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=16, name=ESP_AES_CCM_C, ivlen=8, keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=18, name=ESP_AES_GCM_A, ivlen=8, keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=19, name=ESP_AES_GCM_B, ivlen=8, keysizemin=128, keysizemax=256
000 algorithm ESP encrypt: id=20, name=ESP_AES_GCM_C, 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=0, name=(null), blocksize=16, keydeflen=131
000 algorithm IKE encrypt: id=3, name=OAKLEY_BLOWFISH_CBC, blocksize=8, keydeflen=128
000 algorithm IKE encrypt: id=5, name=OAKLEY_3DES_CBC, blocksize=8, keydeflen=192
000 algorithm IKE encrypt: id=7, name=OAKLEY_AES_CBC, blocksize=16, keydeflen=128
000 algorithm IKE encrypt: id=65004, name=OAKLEY_SERPENT_CBC, blocksize=16, keydeflen=128
000 algorithm IKE encrypt: id=65005, name=OAKLEY_TWOFISH_CBC, blocksize=16, keydeflen=128
000 algorithm IKE encrypt: id=65289, name=OAKLEY_TWOFISH_CBC_SSH, blocksize=16, keydeflen=128
000 algorithm IKE hash: id=1, name=OAKLEY_MD5, hashsize=16
000 algorithm IKE hash: id=2, name=OAKLEY_SHA1, hashsize=20
000 algorithm IKE hash: id=4, name=OAKLEY_SHA2_256, hashsize=32
000 algorithm IKE hash: id=6, name=OAKLEY_SHA2_512, hashsize=64
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: {curr_cnt, total_cnt, maxsz} :context={0,1,36} trans={0,1,624} attrs={0,1,832}
000
000 "ec2-tunnel-01": 192.168.0.0/19===209.190.164.199<209.190.164.199>[+S=C]... 72.21.109.125<72.21.109.125>[+S=C]===192.168.120.0/21; prospective erouted; eroute owner: #0
000 "ec2-tunnel-01":     myip=unset; hisip=unset;
000 "ec2-tunnel-01":   ike_life: 28800s; ipsec_life: 3600s; rekey_margin: 540s; rekey_fuzz: 100%; keyingtries: 0
000 "ec2-tunnel-01":   policy: PSK+ENCRYPT+TUNNEL+PFS+UP+IKEv2ALLOW+lKOD+rKOD; prio: 19,21; interface: eth1.100;
000 "ec2-tunnel-01":   dpd: action:hold; delay:3; timeout:10;
000 "ec2-tunnel-01":   newest ISAKMP SA: #0; newest IPsec SA: #0;
000 "ec2-tunnel-01":   IKE algorithms wanted: AES_CBC(7)_128-SHA1(2)-MODP1024(2); flags=-strict
000 "ec2-tunnel-01":   IKE algorithms found:  AES_CBC(7)_128-SHA1(2)_160-2,
000 "ec2-tunnel-01":   ESP algorithms wanted: AES(12)_128-SHA1(2); flags=-strict
000 "ec2-tunnel-01":   ESP algorithms loaded: AES(12)_128-SHA1(2)_160
000
000 #1: "ec2-tunnel-01":500 STATE_MAIN_I3 (sent MI3, expecting MR3); EVENT_RETRANSMIT in 21s; lastdpd=-1s(seq in:0 out:0); idle; import:admin initiate
000 #1: pending Phase 2 for "ec2-tunnel-01" replacing #0
000

Steve

-----Original Message-----
From: users-bounces at openswan.org [mailto:users-bounces at openswan.org] On Behalf Of Steve Zeng
Sent: May 17, 2010 3:38 PM
To: Paul Wouters
Cc: users at openswan.org
Subject: Re: [Openswan Users] esp string error: enc_alg not found

> You only show the first packet going out. That does not mean it is working at all.
>If using netkey, no interfaces will appear. If using klips, it will already exist
>before you start.

Oh! That is the only messages I got. And Yes I am using netkey. Is it due to the fact that I did not configure any tunnel interface yet? I will assume that "service ipsec restart" will create the needed tunnel interface for me. But it seems not. 

Steve

-----Original Message-----
From: Paul Wouters [mailto:paul at xelerance.com] 
Sent: May 17, 2010 10:24 AM
To: Steve Zeng
Cc: users at openswan.org
Subject: RE: [Openswan Users] esp string error: enc_alg not found

On Mon, 17 May 2010, Steve Zeng wrote:

> Great! The hand-shaking seems working...
> 
> May 17 16:50:00 fw1 ipsec__plutorun: 002 added connection description "ec2-tunnel-01"
> May 17 16:50:00 fw1 ipsec__plutorun: 104 "ec2-tunnel-01" #1: STATE_MAIN_I1: initiate

You only show the first packet going out. That does not mean it is working at all.

> However, I do not see the tunnel interface yet when I run ifconfig. Do I need to create the tunnel interface manually? I see the following errors when I run " ipsec auto --status":

If using netkey, no interfaces will appear. If using klips, it will already exist
before you start.

Paul
_______________________________________________
Users at openswan.org
http://lists.openswan.org/mailman/listinfo/users
Building and Integrating Virtual Private Networks with Openswan: 
http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155