| To: | netdev@xxxxxxxxxxx |
|---|---|
| Subject: | Re: (usagi-users 02412) IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 |
| From: | "Dr. Peter Bieringer" <pb@xxxxxxxxxxxx> |
| Date: | Thu, 05 Jun 2003 16:20:09 +0200 |
| Cc: | usagi-users@xxxxxxxxxxxxxx |
| In-reply-to: | <35410000.1054818456@klopffest.muc.aerasec.de> |
| References: | <35410000.1054818456@klopffest.muc.aerasec.de> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Ohoh, sorry for confusions, my racoon here was a little bit buggy... ...be warned, not using RHL's ipsec-tools from rawhide...looks like the racoon isn't compiled in a proper environment :-( it doesn't support DES and causes trouble on 3DES *grmml*). The reported 3DES problem was solved now by using a fresh compiled one. But the AES one still occurs. FreeS/WAN: 112 "freeswan-racoon-tunnel" #14: STATE_QUICK_I1: initiate 003 "freeswan-racoon-tunnel" #14: ESP transform ESP_AES passed key_len=32 > 16 032 "freeswan-racoon-tunnel" #14: STATE_QUICK_I1: internal error
112 "freeswan-racoon-tunnel" #15: STATE_QUICK_I1: initiate 003 "freeswan-racoon-tunnel" #15: ESP transform ESP_AES passed key_len=24 > 16 032 "freeswan-racoon-tunnel" #15: STATE_QUICK_I1: internal error Strange, looks like racoon reports always AES key length 16*8, but in raccoon.conf was "aes 192" or "aes 256" specified.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods, James Morris |
|---|---|
| Next by Date: | Re: (usagi-users 02412) IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2, James Morris |
| Previous by Thread: | Re: IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2 (in)compatible encryption methods, James Morris |
| Next by Thread: | Re: (usagi-users 02412) IPsec 2.5.70-bk9 and FreeS/WAN 1.99 with algopatches 0.8.1rc2, James Morris |
| Indexes: | [Date] [Thread] [Top] [All Lists] |