[Openswan Users] Openswan 2.3.1 - signal 6 abort

Paul Wouters paul at xelerance.com
Mon May 16 15:39:38 CEST 2005


On Mon, 16 May 2005, Christopher Moore wrote:

> I'm using Openswan 2.3.1 and if I define a connection with a  with a wildcard
> IP address to a Vigor 2600 router Openswan aborts with signal
> 6.
> I've run gdb on the core file and this is what I get:
>
> #0  0x400be9c1 in __kill () from /lib/libc.so.6
> (gdb) where
> #0  0x400be9c1 in __kill () from /lib/libc.so.6
> #1  0x4002365d in pthread_kill (thread=11209, signo=0) at signals.c:65
> #2  0x4002397b in __pthread_raise (sig=1073917068) at signals.c:187
> #3  0x400be75a in *__GI_raise (sig=6)
>    at ../linuxthreads/sysdeps/unix/sysv/linux/raise.c:34
> #4  0x400bfee7 in *__GI_abort () at ../sysdeps/generic/abort.c:88
> #5  0x08058147 in passert_fail (pred_str=0x80bd6e2 "c->policy & POLICY_OPPO",
>    file_str=0x80bc18f "connections.c", line_no=2614) at log.c:598
> #6  0x08050757 in initiate_opportunistic_body (b=0xbfffe6b0, ac=0x0, ac_ugh=0x0)
>    at connections.c:2614
> #7  0x0804ffb7 in initiate_opportunistic (our_client=0xbfffe770,
>    peer_client=0xbfffe750, transport_proto=0, held=1, whackfd=-1,
>    why=0x80c7ff3 "acquire") at connections.c:2323
> #8  0x0806ff65 in record_and_initiate_opportunistic (ours=0xbfffe7f0,
> his=0xbfffe7d0,
>    transport_proto=0, why=0x80ca4d3 "%acquire-pfkey") at kernel.c:229
> #9  0x08078188 in process_pfkey_acquire (buf=0xbfffe910, extensions=0xbfffe870)
>    at kernel_pfkey.c:401
> #10 0x08078305 in pfkey_async (buf=0xbfffe910) at kernel_pfkey.c:446
> #11 0x080783d8 in pfkey_event () at kernel_pfkey.c:494
> #12 0x0805f48f in call_server () at server.c:1109
> #13 0x0805c04c in main (argc=8, argv=0xbffffbd4) at plutomain.c:747

This bug has been filed as http://bugs.xelerance.com/view.php?id=304

It looks strangely familiar though. Can you update the above issue with
your configuration file on the openswan end? (Or mail me and I'll put it
in).

If possible, can you try and see if this issue has been fixed in HEAD?

What might be the problem is that you are not disabling OE, while running
NETKEY. Are you including /etc/ipsec.d/examples/no_oe.conf in your ipsec.conf?

Paul


More information about the Users mailing list