Hi all,
I try to upgrade from strongswan 4.3.2 to 4.3.4.
But I encountered the following problem. I am not sure what
happened...
Thanks. ^__^""
configure.in:757: error: possibly undefined macro: AC_LIB_PREFIX
If this token and others are legitimate, please use m4_pattern
Busybox doesn't have iproute2. They have a simple utility that "looks
and feels" like iproute2 and it doesn't have support for xfrm and many
other features of iproute2. You'll need to download the proper iproute2
package.
Dimitrios Siganos
Jessie Liu wrote:
> Hi Andreas,
>
>ip route list
Yeah, it looks as if your BusyBox does not support the xfrm subcommand.
Either try to update to a more recent BusyBox or install setkey
from the ipsec-tools package instead:
setkey -D is similar to ip xfrm state
and
setkey -DP similar to ip xfrm policy
Regards
Andreas
Jessie Liu wrote:
>
Hi Andreas,
ip route list works fine on my target board. but ip xfrm state did not work.
When I type "ip xfrm state",
it shows the following messages:
BusyBox v1.10.1 (2009-09-28 15:09:16 CST) multi-call binary
Usage ip [OPTIONS] {address | route | link | tunnel | rule} {COMMAND}
---
Hi Jessie,
in the past there are some embedded platform which did not implement
the ip xfrm command. Does e.g. "ip route list" work? If not then the
whole iproute2 package is missing and you must install it first.
Regards
Andreas
Jessie Liu wrote:
> Hi all,
> I'am trying to use " ip xfrm stat
Hi all,
I'am trying to use " ip xfrm state " and " ip xfrm policy " command.
But I couldn't use that command to show information. There is no such command!
What else should I add in kernel config?
I already have xfrm4_tunnel.ko and xfrm_user.ko, but still cannot use that
command.
Thanks a lot.
Thanks very much for your help.
I am using ARM926EJ-S rev 5, not ARM11.
--- 09/9/29 (二)，Martin Willi 寫道：
寄件者: Martin Willi
主旨: Re: [strongSwan] EAP-AKA authentication -- Received MAC does not match XMAC
收件者: "Jessie Liu"
副本: users@lists.strongswan.org
日期: 2009年9月29日,二,下午2:42
Hi,
> I wil
Hi Martin and Andreas, Hi all,
I found the IPsec tunnel will be "broken" unexpectly after a long time no
data pass through it. And I have enabled DPD mechanism in ipsec.conf as
followed:
Keyingtries=%forever
...
dpdaction=clear
dpdtimeout=5m
dpddelay=10
I only configured DPD on
