From: M. N. <joa...@in...> - 2006-09-10 10:40:23
|
Good morning, Seems like something is trying to read the wrong key from psk.txt or not even the right key. In searching for a problem in my configuration I patched the HEAD with the patch below. The idea is to give an ERROR to the log with the key behind read from the psk.txt and the key being searched for. The result indicates that the key for my_identifier is not being searched. A grep by ERROR in the log provides: 2006-09-10 11:36:19: ERROR: AWi...@cp...A-A��A 2006-09-10 11:36:19: ERROR: ARMLZA-A��A 2006-09-10 11:36:19: ERROR: AWi...@cp...A-A213.58.140.26A 2006-09-10 11:36:19: ERROR: ARMLZA-A213.58.140.26A 2006-09-10 11:36:19: ERROR: couldn't find the pskey for 213.58.140.26. repeated for each attempt. Seems like my problem is more basic than I thought. I'll keep you posted on any updates and I'd welcome any hints. You can find my racoon.conf attached. Index: localconf.c =================================================================== RCS file: /cvsroot/ipsec-tools/ipsec-tools/src/racoon/localconf.c,v retrieving revision 1.9 diff -u -r1.9 localconf.c --- localconf.c 17 Apr 2005 16:53:47 -0000 1.9 +++ localconf.c 10 Sep 2006 10:32:28 -0000 @@ -209,6 +209,9 @@ if (*p == '\0') continue; /* no 2nd parameter */ p--; + plog(LLV_ERROR, LOCATION, NULL, + "A%sA-A%sA\n", buf, str); + if (strncmp(buf, str, len) == 0 && buf[len] == '\0') { p++; keylen = 0; Thanks in advance, João Miguel Neves |