During setup of StrongSWAN the ebuild tries to get the version of the currently installed kernel by looking for the string "UTS_RELEASE" in the file "/usr/src/linux/include/linux/version.h" (line 41 of strongswan-2.5.7.ebuild). But as of kernel version 2.6.18 the string "UTS_VERSION" is no longer stored in the file version.h but in utsrelease.h in the same directory. Therefore starting with kernel version 2.6.18 not only the file version.h but also the file utsrelease.h should be considered for finding out the version of the currently installed kernel. Thx a lot for your support GENTOO RULEZ!
I'm working on an updated ebuild.
I added strongswan-2.8.0 to portage, which can handle newer kernel. It's still ~arch only and I have to wait the 30 days for stabilisation. Testing of that version is appreciated! :)
Thanks a lot for the fast resolution. I will try it next week and provide further feedback.
The new strongswan-2.8.0 ebuild seems to work perfectly with newer (>2.6.18) and older (< 2.6.18) kernel versions. No problem to compile and also no problem to establish a tunnel (even with older strongswan on the other side).
That's great to hear! I tested it in a setup with openswan on the other side only. I'll make this version stable at the beginning of January (we have to wait four weeks until a new added ebuild can be stabilised).
Just to confirm it once again. Works great for a couple of weeks. I have one central gateway and 5 gateways connecting to it. There are also about 10 roadwarriors (WinXP with NCP IPSec clients) using the gateway with no problems so far.
