[Openswan Users] Do I need to patch the kernel to build OCF with Openswan?

Ankit Parikh anks.capri20 at gmail.com
Fri Jul 20 14:10:51 EDT 2007

Tried patching and grep too , but without much success!!! the problem seems
to be with ipsec only !!! I installed openswan 2.4.7 and just did ipsec and
everything worked fine !! but if I use openswan 3.0.06 then, the problems
arise...This is the output I get...

root at localhost openswan-3.0.06]# service ipsec start
ipsec_setup: Starting Openswan IPsec 3.0.06GITGITGIT...
ipsec_setup: FATAL: Error inserting ipsec
(/lib/modules/ Unknown symbol in module,
or unknown parameter (see dmesg)
ipsec_setup: calcgoo: warning: 2.6 kernel with kallsyms not supported yet
ipsec_setup: insmod /lib/modules/
ipsec_setup: FATAL: Error inserting padlock
(/lib/modules/ No such device
ipsec_setup: insmod /lib/modules/
ipsec_setup: FATAL: Error inserting ipsec
(/lib/modules/ Unknown symbol in module,
or unknown parameter (see dmesg)
ipsec_setup: kernel appears to lack IPsec support (neither CONFIG_KLIPS or

What does these means? Error inserting ipsec, error inserting padlock ????
There some unknown symbol in the module....what is the meaning of that?


On 7/19/07, David McCullough <David_Mccullough at securecomputing.com> wrote:
> Jivin Ankit Parikh lays it down ...
> > I am sorry for so many posts and flooding the mailing lists, but I am
> new to
> > everything..including linux and openswan..Plz don't mind..
> No probs.
> > I am running the new kernel which i recompiled. I recompiled the same
> > version of the kernel. ( Here is what I get by dmesg. I
> observed
> > one thing while the comp. boots. When IPSec service starts, it prints
> out
> > that neither CONFIG_KLIPS or
> > CONFIG_NET_KEY are set and it fails and the booting of other services
> > continues.
> Those errors are from pluto and the user apps because the ipsec
> driver is failing to load.
> ...
> > NET: Registered protocol family 31
> > Bluetooth: HCI device and connection manager initialized
> > Bluetooth: HCI socket layer initialized
> > Bluetooth: L2CAP ver 2.8
> > Bluetooth: L2CAP socket layer initialized
> > Bluetooth: RFCOMM socket layer initialized
> > Bluetooth: RFCOMM TTY layer initialized
> > Bluetooth: RFCOMM ver 1.8
> > Bluetooth: HIDP (Human Interface Emulation) ver 1.1
> > ipsec: Unknown symbol abort
> > padlock: VIA PadLock not detected.
> > ipsec: Unknown symbol abort
> This is your problem,  ipsec is calling abort(),  yet there is no such
> kernel function.  Try the attached patch.  Perhaps run a grep across
> you openswan/linux tree for abort if this doesn't fix it.
> Cheers,
> Davidm
> --
> David McCullough,  david_mccullough at securecomputing.com,   Ph:+61
> 734352815
> Secure Computing - SnapGear  http://www.uCdot.org
> http://www.cyberguard.com

Ankit Parikh
MS, Computer Science
University of Southern California
Los Angeles
(M) 213.448.9394
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20070720/aca3cc6c/attachment.html 

More information about the Users mailing list