On Tue, 2012-08-07 at 10:51 +0200, Erik K. wrote:
Hi all, i have tried that and after a
[root@ipfire-server ~]# /etc/init.d/ipsec start Starting strongSwan 5.0.0 IPsec [starter]... insmod /lib/modules/2.6.32.45-ipfire/kernel/net/key/af_key.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/ipv4/ah4.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/ipv4/esp4.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/xfrm/xfrm_ipcomp.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/ipv4/ipcomp.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/ipv4/tunnel4.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/ipv4/xfrm4_tunnel.ko insmod /lib/modules/2.6.32.45-ipfire/kernel/net/xfrm/xfrm_user.ko
there was no output on httpd/error_log
It is not supposed that there is any.
but my log manager warned me per email with a:
OSSEC HIDS Notification. 2012 Aug 07 10:29:16
Received From: ipfire-server->/var/log/messages Rule: 1002 fired (level 2) -> "Unknown problem somewhere in the system." Portion of the log(s):
Aug 7 10:29:16 ipfire-server charon: 00[LIB] plugin 'padlock': failed to load - padlock_plugin_create returned NULL
--END OF NOTIFICATION
Well, that's bad from your log manager.
strongswan tries to use hardware crypto when it is available. So it loads the padlock module which fails to load with an error saying there is not padlock available. Which is totally normal on an Intel PC.
This is nothing harmful, but the program shouldn't notify.
Also is there a dev list with changes on this new version especially for the WUI so the documentation can start up more quickly ?
No, we are still testing those changes.
If we can be sure that there are no more severe problems, we can start the documentation. At this stage, it might be possible that changes in the UI are required.
Please do a little more testing...
Michael