From: Hardik A Gohil <hardik@willowglen.com.my>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OPENSWAN IPSEC Configuration
Date: Fri, 31 Jul 2015 16:34:57 +0800 [thread overview]
Message-ID: <CAEZH62OW_PKxHX3xNR1adn8ZeMFqLu-Gn_eqOC3rktvvhuMk9w@mail.gmail.com> (raw)
In-Reply-To: <915054555B5659448ACF8A70E114824D01BD2D06A0@Exchange2010.kamstrup.dk>
[-- Attachment #1.1: Type: text/plain, Size: 2485 bytes --]
Hello,
I am getting this error when ipsec start is given.
output of log :
Jul 30 23:26:42 phyCORE-AM335x user.info kernel: [ 46.746368] NET:
Registered protocol family
15
Jul 30 23:26:42 phyCORE-AM335x user.info kernel: [ 46.885162]
Initializing XFRM netlink
socket
Jul 30 23:26:42 phyCORE-AM335x daemon.info charon: 00[DMN] Starting IKE
charon daemon (strongSwan 5.3.2, Linux 3.2.0-PD13.1.2, armv7l)
Jul 30 23:26:42 phyCORE-AM335x daemon.info charon: 00[LIB] feature
CUSTOM:libcharon in critical plugin 'charon' has unmet dependency:
NONCE_GEN
Jul 30 23:26:42 phyCORE-AM335x daemon.info charon: 00[LIB] feature
CUSTOM:libcharon-receiver in critical plugin 'charon' has unmet dependency:
HASHER:HASH_SHA1
Jul 30 23:26:42 phyCORE-AM335x daemon.info charon: 00[LIB] failed to load 2
critical plugin features
Jul 30 23:26:42 phyCORE-AM335x daemon.info charon: 00[DMN] initialization
failed - aborting charon
Jul 30 23:26:42 phyCORE-AM335x authpriv.info ipsec_starter[852]: charon has
quit: initialization failed
Jul 30 23:26:42 phyCORE-AM335x authpriv.info ipsec_starter[852]: charon
refused to be started
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: received
netlink error: Operation not supported (95)
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: unable to
create IPv4 routing table rule
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: received
netlink error: Operation not supported (95)
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: unable to
create IPv6 routing table rule
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: received
netlink error: Operation not supported (95)
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: received
netlink error: Operation not supported (95)
Jul 30 23:26:43 phyCORE-AM335x authpriv.info ipsec_starter[852]: ipsec
starter stopped
~
On Thu, Jul 30, 2015 at 6:09 PM, Bruno Thomsen <bth@kamstrup.com> wrote:
> Hi,
>
> > I am looking for strongswan.make file.
>
> You can find the newest upstream strongswan rule[1][2] in the pengutronix
> ptxdist git repository[3].
>
>
> [1]
> http://git.pengutronix.de/?p=ptxdist.git;a=blob_plain;f=rules/strongswan.in;hb=HEAD
> [2]
> http://git.pengutronix.de/?p=ptxdist.git;a=blob_plain;f=rules/strongswan.make;hb=HEAD
> [3] http://git.pengutronix.de/?p=ptxdist.git;a=summary
>
>
> /Bruno
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Regards
Hardik A Gohil
Willowglen Msc Bhd
[-- Attachment #1.2: Type: text/html, Size: 5194 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-31 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 3:58 Hardik A Gohil
2015-07-23 5:56 ` Bruno Thomsen
2015-07-30 9:18 ` Hardik A Gohil
2015-07-30 10:09 ` Bruno Thomsen
2015-07-31 8:34 ` Hardik A Gohil [this message]
2015-07-29 8:03 Hardik A Gohil
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=CAEZH62OW_PKxHX3xNR1adn8ZeMFqLu-Gn_eqOC3rktvvhuMk9w@mail.gmail.com \
--to=hardik@willowglen.com.my \
--cc=ptxdist@pengutronix.de \
/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