[Openswan Users] Openswan 2.4.6rc5 under CentOS 4.3

Bas Rijniersce bas at brijn.nu
Tue Aug 15 15:50:41 EDT 2006


Hello,

I'm trying to get Openswan running in a CentOS 4.3 environment. I want to 
modify as little as possible so that the machine can be kept up to date 
easily. I'd rather not compile a special kernel, but if that's the only 
solution, no problem.

It's running kernel 2.6.9-34.0.2.EL. Installed the kerneldevel RPM (and 
kernel src rpm as well). I compiled openswan with:
make KERNELSRC=/lib/modules/`uname -r`/build/ module minstall (and same for 
progs)

Module seems to load fine, lsmod shows as loaded. I do get quite a bit of 
output on the console that I don't know is normal:
----
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:ipsec_eroute_get_info: 
buffer=0pc9cce000, *start=0p00000000, offset=61, length=1024
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: for: 
rn=0pcce7a5a8 rj_b=-3 rj_flags=6 leaf key = 00000000->00000000
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: processing 
leaves, rn=0pcfc9c280 rj_b=-1 rj_flags=4 leaf key = 0a010000->0a020000
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: while: 
base=0p00000000 rn=0pcce7a5a8 rj_b=-3 rj_flags=6 leaf key = 
00000000->00000000
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: for: 
rn=0pcfc9c280 rj_b=-1 rj_flags=4 leaf key = 0a010000->0a020000
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: processing 
leaves, rn=0pcce7a5d8 rj_b=-3 rj_flags=6 leaf key = ffffffff->ffffffff
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:rj_walktree: while: 
base=0p00000000 rn=0pcfc9c280 rj_b=-1 rj_flags=4 leaf key = 
0a010000->0a020000
Aug 15 12:44:15 INAKFW001 kernel: klips_debug:ipsec_rj_walker_procprint: 
rn=0pcfc9c280, w0=0pcc83df20
----

The problem is when I restart the machine, or just restart the service. I 
panic's :-) Not a good thing for a box that will be hidden in a closet in 
India :)

I video of the crash can be found at: http://www.brijn.nu/openswan_crash.avi 
(151Kb)

This machine is running in VMware at the moment. I have the same problem in 
a "real" machine (identical setup)

Can I build the module as I did, should that work OK? Any other suggestion 
on what might be wrong?

Thank you very much for your time!

Bas





More information about the Users mailing list