From: "Erik K." <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Development] Strongswan 5.0.0
Date: Tue, 07 Aug 2012 11:24:16 +0200 [thread overview]
Message-ID: <81936975-6546-419A-A1F4-A4C78C6EB213@ipfire.org> (raw)
In-Reply-To: <1344330783.7540.39.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 2294 bytes --]
Am 07.08.2012 um 11:13 schrieb Michael Tremer:
> On Tue, 2012-08-07 at 10:51 +0200, Erik K. wrote:
>>
>>> Hi all,
>>> i have tried that and after a
>>>
>>> [root(a)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
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
Ah O.K. my fault sorry
Thanks for information
next prev parent reply other threads:[~2012-08-07 9:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0F362495-84A1-4E4E-9420-34BF53F4595F@ipfire.org>
2012-08-07 9:13 ` Michael Tremer
2012-08-07 9:24 ` Erik K. [this message]
2012-08-03 12:58 Michael Tremer
2012-08-06 15:21 ` Stefan Schantl
2012-08-06 15:36 ` Michael Tremer
2012-08-06 19:48 ` Stefan Schantl
2012-08-06 21:11 ` Michael Tremer
2012-08-07 11:09 ` Stefan Schantl
2012-08-07 15:08 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81936975-6546-419A-A1F4-A4C78C6EB213@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox