Hi all, First of all: thanks to all of you who have contributed to Bering-uClibc, it's really a pleasure to use.
I have recently upgraded my existing Bering-uClibc 2.x boxes to version 3.02 and ipsec compression doesn't work anymore. If I turn compression on (compress=yes) the connection negotiation will fail with an EVENT_CRYPTO_FAILED on one side (the site not initiating the connection). When turning on detailed logging I can see that the extensions required and seen do not match (00000001 versus 00000063). I must confess that I have failed to find what extensions these numbers represent, but I expect some of you will know. After some digging around I noticed that the kernel has been built with CONFIG_KLIPS_IPCOMP not set and I'm wondering whether this is the cause of the problem and whether it has been turned off for a reason. CONFIG_KLIPS_ALG is set and I may have to use the cryptoapi algorithms and their deflate support. Much to my regret I have not been able to get that working, either. Browsing through the archives I get the impression that I may not be the only one with that problem. Could you advise me as to which of the following options I should consider: 1. Repost in leaf-user. This is a configuration issue and the kernel config has nothing to do with it. Sorry to have posted here :-). 2. Try and get the cryptoapi algorithms working. 3. Recompile the kernel with KLIPS_IPCOMP support turned on. Thanks a lot, Tekke Bosman ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
