Hi Erich, >>> - replace openswan with strongswan and still track current kernel >>> development/configuration.. >> don't know about that one - the whole *swan integration into the kernel >> is a bit obscure (due to the fact that the buildenv needs the kernel >> sources, but to build a kernel, you need a buildenv...) > > Sure, and I want to use the existing one, now I could probably modify > the kernel target to use a different *swan. > Note that unlike openswan, strongswan doesn't have a seperate patchset. So you need to patch the kernel with the strongswan source tools itself, build the buildenv and after that build strongswan.
Eric _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
