Using buildtool to build openswan for bering-uclibc 2.3 beta (kernel
2.4.29). Copy ipsec.lrp to LEAF box... everything seems normal except
ipsec does not load ipsec_aes.o like it used to before.
This becomes more of a problem when I want to:
svi ipsec stop (or restart) because it cannot unload ip
cpu memhd wrote:
Using buildtool to build openswan for bering-uclibc 2.3 beta (kernel
2.4.29). Copy ipsec.lrp to LEAF box... everything seems normal except
ipsec does not load ipsec_aes.o like it used to before.
IIRC this was never loaded by the original (FreeSWan) code. It is pretty
trivial to
Okay... I still think something is wrong. This is what
/etc/init.d/ipsec start is doing:
ipsec_setup: Starting Openswan IPsec 1.0.9...
insmod: not an ELF file
insmod: Could not load the module: Success
ipsec_setup: Using ipsec
ipsec_setup: Using /lib/modules/ipsec.o
_startklips has this line some
Hello cpu,
This is a strange message:
"insmod: not an ELF file"
Can you run insmod from the command line?
"errors out here because /lib/modules is not in my path
and it's trying to load the ipsec executable.
Should /lib/modules be in the path (presumably the start)?"
Insmod looks at /lib/modul
Eric,
It looks like it's trying to load /lib/ipsec/ipsec (the shell script).
Does insmod default to the current directory? Perhaps the ipsec scripts
are being run from within /lib/ipsec.
Everywhere else it loads fine:
foobar# insmod ipsec
Using /lib/modules/ipsec.o
Here are some of the changes
Cpu,
>Eric,
>
>It looks like it's trying to load /lib/ipsec/ipsec (the shell
>script).
>Does insmod default to the current directory? Perhaps the ipsec
>scripts
>are being run from within /lib/ipsec.
No insmod shouldn't default to the current directory, just tested it
myself and ipsec is loade
Eric,
Thanks for the help. I followed your instructions in a previous post on
building the minimum packages after a kernel build: modules, initrd,
and root.lrp. ipsec was also built/packaged from the same kernel.
Today I tried beta 2.3:
1. Downloaded linux-2.4.29.upx (renamed to linux), initrd_i
Hello Cpu,
Thanks for testing.
I also did the same as you did and see the same behaviour, insmod
trying to load the "module" in the current directory.
This is a busybox bug, not much I can do about unfortuanatly. It's
probably in there since years. I will report it on the busybox list.
Luckely
