[Openswan Users] Weird module thingie

Paul Wouters paul at xelerance.com
Sat Jan 21 00:50:15 CET 2006

On Fri, 20 Jan 2006, Radek Antoniuk wrote:

> I've posted a bug http://bugs.xelerance.com/view.php?id=561
> and well. I'm now confused.
> If I try to insert the module into kernel with modprobe... I get the
> mentioned oops.
> BUT, if I won't insert it, and do ipsec setup --start, everything works
> great.
> So:
> 1) why inserting doesn't work?
> 2) if there is no ipsec module loaded, and no ipsec support is compiled
> into kernel, how does ipsec actually work?
> I've came up with an obvious idea. I've selected in make menuconfig all
> Openswan options to be built into kernel, not by module. But even if
> that's the case, it should not make an oops, but give an error instead.
> So, where am I?

There are two ipsec stacks, NETKEY and KLIPS. The 2.6 kernel comes with
NETKEY, consisting of the kernel modules xfrm_user,esp4,ah4,xfrm4_tunnel,af_key.
KLIPS is ipsec.ko

You are probably now using NETKEY.


"Happiness is never grand"

	--- Mustapha Mond, World Controller (Brave New World)

More information about the Users mailing list