[Openswan Users] Openswan and RHEL 3 error xfrm_user module

[Nicole Hähnel]

I think the messages are errors.
I can't find any modules with this names in configs.

And there is no ipsec interface after starting ipsec.
So they seem to be errors!


Nicole


Graham Leggett wrote:

> Nicole Hähnel wrote:
> 
>> Either openswan cannot use it, or the configs include it, but the 
>> kernel was not compiled with it by mistake of redhat?
>> Is there a way to check if running kernel provides the function?
>> But the log continues with errors:
>>
>> Jun 28 10:35:29 VPN ipsec_setup: Starting Openswan IPsec 
>> U2.1.2/K2.4.21-15.0.2.EL...
>> Jun 28 10:35:29 VPN ipsec_setup: modprobe: Can't locate module xfrm_user
>> Jun 28 10:35:29 VPN ipsec_setup: KLIPS ipsec0 on ppp0 
>> xx.xx.xx.xx/255.255.255.255 pointopoint xx.xx.xx.xx
>> Jun 28 10:35:29 VPN ipsec_setup: ...Openswan IPsec started
>> Jun 28 10:35:29 VPN modprobe: modprobe: Can't locate module ripemd160
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module cast128
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzs
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzjh
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module ripemd160
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module cast128
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzs
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzjh
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module ripemd160
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module cast128
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzs
>> Jun 28 10:35:30 VPN modprobe: modprobe: Can't locate module lzjh
> 
> 
> Are the above messages errors, or are they just informational warnings?
> 
> The messages themselves indicate that the modules could not be loaded - 
> but if the modules were compiled into the kernel by Redhat, then the 
> modules cannot be loaded, but this is not an error condition, because 
> the modules are built into the kernel anyway.
> 
> Regards,
> Graham
> -- 
>