Discussion:
[Openswan Users] pluto failure
Marco Berizzi
2005-04-26 15:20:50 UTC
Permalink
Hello.
I'm running OpenSWAN 2.3.1 on Slackware 10.1
I have manually patched (make kpatch) linux
vanilla 2.4.30
Gcc is 3.3.5, glibc 2.3.4
Today, after about 10 uptime days pluto has
been crashed.
Here is syslog:

Apr 20 17:39:31 Pleiadi kernel: klips_error:ipsec_xmit_send: ip_send()
failed, err=1
Apr 26 16:24:32 Pleiadi ipsec__plutorun: /usr/local/lib/ipsec/_plutorun:
line 221: 8417 Aborted
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
Apr 26 16:24:32 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
Apr 26 16:24:32 Pleiadi ipsec__plutorun: restarting IPsec after pause...
Apr 26 16:24:43 Pleiadi kernel: IPSEC EVENT: KLIPS device ipsec0 shut
down.
Apr 26 16:24:43 Pleiadi kernel:
Apr 26 16:24:43 Pleiadi ipsec_setup: ...Openswan IPsec stopped
Apr 26 16:24:43 Pleiadi ipsec_setup: Stopping Openswan IPsec...
Apr 26 16:24:43 Pleiadi ipsec_setup: Removing orphaned
/var/run/pluto/pluto.pid:
Apr 26 16:24:44 Pleiadi ipsec_setup: KLIPS debug `none'
Apr 26 16:24:44 Pleiadi kernel:

It's impossible for me reproduce this error :-((
Any feedback are welcome.
PS: Kernel is NAT-T enbled.
Alan Tamer Vasques
2005-04-26 15:45:32 UTC
Permalink
Hi, folks,

I'm trying to configure a IPSec/L2TP linux client, but I'm facing some
little troubles.

Basically, the IPSec tunnel is stablished successfully, but the L2TP/PPP
authentication fails.

The first problem is that, looking at /var/log/messages in my VPN Server, it
says that the user is my client's hostname and not a real user that I want.

Then, I configure my options.l2tpd file on the VPN Server to not perform
authentication (noauth). Then, the ppp0 appears on both sides, but the
server can't determine the Ethernet address of my client with the "proxyarp"
option.

Anybody could help me, please?

Regards,

Alan Tamer Vasques
Jacco de Leeuw
2005-04-26 21:25:13 UTC
Permalink
Post by Alan Tamer Vasques
I'm trying to configure a IPSec/L2TP linux client, but I'm facing some
little troubles.
Basically, the IPSec tunnel is stablished successfully, but the L2TP/PPP
authentication fails.
The first problem is that, looking at /var/log/messages in my VPN Server, it
says that the user is my client's hostname and not a real user that I want.
You can specify the 'user' option in options.l2tpd.
See 'man pppd'.
Post by Alan Tamer Vasques
Then, I configure my options.l2tpd file on the VPN Server to not perform
authentication (noauth). Then, the ppp0 appears on both sides, but the
server can't determine the Ethernet address of my client with the "proxyarp"
option.
Both sides run Linux? I would not recommend L2TP for such a setup.
IPsec without L2TP is easier to use.

Jacco
--
Jacco de Leeuw mailto:***@dds.nl
Zaandam, The Netherlands http://www.jacco2.dds.nl
Tomasz Grzelak
2005-04-27 06:25:21 UTC
Permalink
Post by Jacco de Leeuw
Both sides run Linux? I would not recommend L2TP for such a setup.
IPsec without L2TP is easier to use.
Sorry for interrupting the topic but I think it's right time to ask, how
do you handle issues with MTU when using plain IPSec?
If you had L2TP/PPP, you could set an MTU in ppp to some lower value to
balance the overhead added by IPSec protocol encapsulation. I noticed
that xp native (L2TP/PPP) clients had no MTU problem. Correct me if I am
wrong.

I configured a tunnel between two linux hosts running OpenSwan 2.2.0
with plain IPSec, and no other layer 2 protocols, and I had big troubles
to make rdp/vnc/smb connections work, while other light connections
(example: telnet, ssh) worked fine.

I finally used the MSS target in the iptables script, and it all worked
fine.
Unfortunatelly I am not able to check if Path-MTU (as I remember it is
icmp [type 3, code 4]) would also work.
If you open a firewall for this icmp traffic, would it be enough?

I'd like to ask how you handle such problems.

Tomasz Grzelak
Tomasz Grzelak
2005-04-27 13:21:55 UTC
Permalink
Post by Tomasz Grzelak
Sorry for interrupting the topic but I think it's right time to ask,
how do you handle issues with MTU when using plain IPSec?
Sorry, you're asking the wrong guy. I have not had MTU problems
(fortunately) so I can't really help.
so you are the lucky one :)
How about using 'ifconfig eth0 mtu 1400' or some other value?
that's not an option; there is a lot of other traffic on the IPSec link

I just want to know how it should be solved best - establish
PPP/L2TP/IPSec connections like xp clients do, or would be enough to let
icmp [3,4] packets go through, so Path-MTU would be used, or... what else?

I used the MSS target in the iptables script, and it worked, but I think
it isn't the right way, bacause it does not solve all problems, just TCP
sessions.

So, who else had the problem, and would like to share the knowledge of
solving it?

Tomasz Grzelak
Jorge Daniel Sequeira Matias
2005-04-26 17:21:54 UTC
Permalink
I have a similar setup (difference is in dist. used) and Paul Wouters told
me that this problem is solved in CVS HEAD. It will be corrected in Openswan
2.3.2.
I have not tested yet but I'll do the tests very soon.

Jorge Matias
Post by Marco Berizzi
Hello.
I'm running OpenSWAN 2.3.1 on Slackware 10.1
I have manually patched (make kpatch) linux
vanilla 2.4.30
Gcc is 3.3.5, glibc 2.3.4
Today, after about 10 uptime days pluto has
been crashed.
Apr 20 17:39:31 Pleiadi kernel: klips_error:ipsec_xmit_send: ip_send()
failed, err=1
line 221: 8417 Aborted
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
Apr 26 16:24:32 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
Apr 26 16:24:32 Pleiadi ipsec__plutorun: restarting IPsec after pause...
Apr 26 16:24:43 Pleiadi kernel: IPSEC EVENT: KLIPS device ipsec0 shut
down.
Apr 26 16:24:43 Pleiadi ipsec_setup: ...Openswan IPsec stopped
Apr 26 16:24:43 Pleiadi ipsec_setup: Stopping Openswan IPsec...
Apr 26 16:24:43 Pleiadi ipsec_setup: Removing orphaned
Apr 26 16:24:44 Pleiadi ipsec_setup: KLIPS debug `none'
It's impossible for me reproduce this error :-((
Any feedback are welcome.
PS: Kernel is NAT-T enbled.
_______________________________________________
Users mailing list
http://lists.openswan.org/mailman/listinfo/users
Paul Wouters
2005-04-26 21:11:21 UTC
Permalink
Post by Marco Berizzi
I'm running OpenSWAN 2.3.1 on Slackware 10.1
I have manually patched (make kpatch) linux
vanilla 2.4.30
Gcc is 3.3.5, glibc 2.3.4
Today, after about 10 uptime days pluto has
been crashed.
Apr 20 17:39:31 Pleiadi kernel: klips_error:ipsec_xmit_send: ip_send()
failed, err=1
line 221: 8417 Aborted
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
Apr 26 16:24:32 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
Please add dumpdir=/tmp to config setup and restart openswan. When the
failire happens again, you should have a core file. Use gdb on it to give
us a backtrace.

Paul
Marco Berizzi
2005-04-27 12:22:30 UTC
Permalink
Post by Paul Wouters
Post by Marco Berizzi
I'm running OpenSWAN 2.3.1 on Slackware 10.1
I have manually patched (make kpatch) linux
vanilla 2.4.30
Gcc is 3.3.5, glibc 2.3.4
Today, after about 10 uptime days pluto has
been crashed.
ip_send()
Post by Paul Wouters
Post by Marco Berizzi
failed, err=1
line 221: 8417 Aborted
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
Apr 26 16:24:32 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
Please add dumpdir=/tmp to config setup and restart openswan. When the
failire happens again, you should have a core file. Use gdb on it to give
us a backtrace.
Paul
Done.
Thanks.
Giovani Moda - MR Informática
2005-04-27 13:09:43 UTC
Permalink
Hi folks,

I've compiled a new kernel (2.6.12-rc3) from source on a FC3 system.
Everything went well,.but when I try to compile the openswan KLIPS module
against the new kernel source, I get the following error:

/tmp/mod26/pfkey_v2.c: In function `pfkey_create':
/tmp/mod26/pfkey_v2.c:654: warning: passing arg 3 of `sk_alloc' makes
pointer from integer without a cast
/tmp/mod26/pfkey_v2.c:654: warning: passing arg 4 of `sk_alloc' makes
integer from pointer without a cast
/tmp/mod26/pfkey_v2.c:682: error: structure has no member named `sk_zapped'
/tmp/mod26/pfkey_v2.c: In function `pfkey_get_info':
/tmp/mod26/pfkey_v2.c:1486: error: structure has no member named `sk_zapped'

Has anyone seen an error like this? Is that something I've done wrong at the
kernel compilation? Or is that just my incredible stupidity at work?


Giovani
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25/04/2005
Giovani Moda - MR Informática
2005-04-27 13:39:36 UTC
Permalink
Hey,

I've found this in a forum. I don't really know if it has something to do
with this error, but it appears to me that has been some changes in how
sk_alloc works in these new kernels.

Take a look:

-----------------------------------------------------------------------------------------------------------------------------------------------------------------
Hi everybody,

the 26th of March 2005 Arnaldo Carvalho de Melo commited a quite big change
to
sk_alloc:

ChangeSet 1.2181.42.2 2005/03/26 20:04:49 ***@xxxxxxxxxxxxxxxxxxxxxx
[NET] make all protos partially use sk_prot

sk_alloc_slab becomes proto_register, that receives a struct proto not
necessarily
completely filled, but at least with the proto name, owner and obj_size
(aka proto
specific sock size), with this we can remove the struct sock sk_owner and
sk_slab,
using sk->sk_prot->{owner,slab} instead.

This patch also makes sk_set_owner not necessary anymore, as at sk_alloc
time we
have now access to the struct proto onwer and slab members, so we can bump
the
module refcount exactly at sock allocation time.

Another nice "side effect" is that this patch removes the generic
sk_cachep slab
cache, making the only last two protocols that used it use just kmalloc,
informing
a struct proto obj_size equal to sizeof(struct sock).

Ah, almost forgot that with this patch it is very easy to use a slab
cache, as it is
now created at proto_register time, and all protocols need to use
proto_register,
so its just a matter of switching the second parameter of proto_register
to '1', heck,
this can be done even at module load time with some small additional
patch.

Another optimization that will be possible in the future is to move the
sk_protocol
and sk_type struct sock members to struct proto, but this has to wait for
all protocols
to move completely to sk_prot.

This changeset also introduces /proc/net/protocols, that lists the
registered protocols
details, some may seem excessive, but I'd like to keep them while working
on further
struct sock hierarchy work and also to realize which protocols are old
ones, i.e. that
still use struct proto_ops, etc, yeah, this is a bit of an exaggeration,
as all protos
still use struct proto_ops, but in time the idea is to move all to use
sk->sk_prot and
make the proto_ops infrastructure be shared among all protos, reducing one
level of
indirection.

Signed-off-by: Arnaldo Carvalho de Melo <***@xxxxxxxxxxxxxxxx>
Signed-off-by: David S. Miller <***@xxxxxxxxxxxxx>

The same change needs to be propagated to cman-kernel (probably more,
but i am working on one module at a time).
Here is a preliminary patch that works for me.

Please review before applying.

Signed-off-by: Fabio M. Di Nitto <***@xxxxxxxxxx>

Index: cnxman.c
===================================================================
RCS file: /cvs/cluster/cluster/cman-kernel/src/cnxman.c,v
retrieving revision 1.55
diff -u -r1.55 cnxman.c
- --- cnxman.c 5 Apr 2005 13:43:09 -0000 1.55
+++ cnxman.c 16 Apr 2005 08:20:42 -0000
@@ -66,8 +66,8 @@
extern void cman_set_realtime(struct task_struct *tsk, int prio);

static struct proto_ops cl_proto_ops;
+static struct proto cl_proto;
static struct sock *master_sock;
- -static kmem_cache_t *cluster_sk_cachep;

/* Pointer to the pseudo node that maintains quorum in a 2node system */
struct cluster_node *quorum_device = NULL;
@@ -918,14 +918,14 @@
return;
}

- -static struct sock *cl_alloc_sock(struct socket *sock, int gfp)
+static struct sock *cl_alloc_sock(struct socket *sock, int gfp, int
protocol)
{
struct sock *sk;
struct cluster_sock *c;

if ((sk =
- - sk_alloc(AF_CLUSTER, gfp, sizeof (struct cluster_sock),
- - cluster_sk_cachep)) == NULL)
+ sk_alloc(AF_CLUSTER, gpf, &cl_proto,
+ 1)) == NULL)
goto no_sock;

if (sock) {
@@ -937,6 +937,7 @@
sk->sk_no_check = 1;
sk->sk_family = PF_CLUSTER;
sk->sk_allocation = gfp;
+ sk->sk_protocol = protocol;

c = cluster_sk(sk);
c->port = 0;
@@ -1031,7 +1032,7 @@
if (!atomic_read(&cnxman_running) && protocol != CLPROTO_MASTER)
return -ENETDOWN;

- - if ((sk = cl_alloc_sock(sock, GFP_KERNEL)) == NULL)
+ if ((sk = cl_alloc_sock(sock, GFP_KERNEL, protocol)) == NULL)
return -ENOBUFS;

sk->sk_protocol = protocol;
@@ -4155,6 +4156,12 @@
.owner = THIS_MODULE,
};

+static struct proto cl_proto = {
+ .name = "CMAN",
+ .owner = THIS_MODULE,
+ .obj_size = sizeof(struct cluster_sock)
+};
+
#ifdef MODULE
MODULE_DESCRIPTION("Cluster Connection and Service Manager");
MODULE_AUTHOR("Red Hat, Inc");
@@ -4166,19 +4173,14 @@
printk("CMAN %s (built %s %s) installed\n",
CMAN_RELEASE_NAME, __DATE__, __TIME__);

- - if (sock_register(&cl_family_ops)) {
- - printk(KERN_INFO "Unable to register cluster socket type\n");
+ if (proto_register(&cl_proto,0) < 0) {
+ printk(KERN_INFO "Unable to register cluster protocol type\n");
return -1;
}

- - /* allocate our sock slab cache */
- - cluster_sk_cachep = kmem_cache_create("cluster_sock",
- - sizeof (struct cluster_sock), 0,
- - SLAB_HWCACHE_ALIGN, 0, 0);
- - if (!cluster_sk_cachep) {
- - printk(KERN_CRIT
- - "cluster_init: Cannot create cluster_sock SLAB cache\n");
- - sock_unregister(AF_CLUSTER);
+ if (sock_register(&cl_family_ops)) {
+ proto_unregister(&cl_proto);
+ printk(KERN_INFO "Unable to register cluster socket type\n");
return -1;
}

@@ -4234,7 +4236,7 @@
cnxman_ioctl32_exit();
#endif
sock_unregister(AF_CLUSTER);
- - kmem_cache_destroy(cluster_sk_cachep);
+ proto_unregister(&cl_proto);
}

module_init(cluster_init);
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.10.3 - Release Date: 25/04/2005
Paul Wouters
2005-04-27 17:00:56 UTC
Permalink
Post by Giovani Moda - MR Informática
I've compiled a new kernel (2.6.12-rc3) from source on a FC3 system.
You will need to use CVS HEAD for that kernel, and perhaps it is currently
even still broken in cvs too.

Paul
Marco Berizzi
2005-05-04 08:59:51 UTC
Permalink
Hi. This morning my OpenS/WAN gateway has
been crashed.
OpenS/WAN doesn't start anymore.
(I haven't rebooted this system, I have replaced
with another one).
This is the message starting OpenS/WAN:

#ipsec setup start
ipsec_setup: Starting Openswan IPsec 2.3.1...
ipsec_setup: /usr/local/libexec/ipsec/klipsdebug: pfkey write failed,
tried to write 72 octets, returning -1 with errno=28.
ipsec_setup: no room in kernel SAref table. Cannot process request.
ipsec_setup: /usr/local/libexec/ipsec/eroute: pfkey write failed,
returning -1 with errno=28.
ipsec_setup: no room in kernel SAref table. Cannot process request.
ipsec_setup: /usr/local/libexec/ipsec/spi: pfkey write failed
(errno=28): no room in kernel SAref table. Cannot process request.

This messages sporadically appear in /var/log/debug

May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_parse:
satype 0 conversion to proto failed for msg_type 4 (delete).
May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_build:
Trouble parsing newly built pfkey message, error=-22.
May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_parse:
satype 0 conversion to proto failed for msg_type 4 (delete).
May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_build:
Trouble parsing newly built pfkey message, error=-22.
May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_parse:
satype 0 conversion to proto failed for msg_type 4 (delete).
May 4 07:12:02 Pleiadi pluto[18782]: | pfkey_lib_debug:pfkey_msg_build:
Trouble parsing newly built pfkey message, error=-22.

This is dmesg output:

lg v=0.8.1-0 (EALG_MAX=255, AALG_MAX=251)
klips_info:ipsec_alg_init: calling ipsec_alg_static_init()
ipsec_aes_init(alg_type=15 alg_id=12 name=aes): ret=0
ipsec_aes_init(alg_type=14 alg_id=9 name=aes_mac): ret=0
ip_conntrack version 2.1 (1280 buckets, 10240 max) - 288 bytes per
conntrack
ip_tables: (C) 2000-2002 Netfilter core team
ipt_recent v0.3.1: Stephen Frost <***@snowman.net>.
http://snowman.net/projects/ipt_recent/
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
XFS mounting filesystem ide0(3,1)
Ending clean XFS mount for filesystem: ide0(3,1)
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 260k freed
Adding Swap: 151160k swap-space (priority -1)
PCI: Found IRQ 9 for device 00:09.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
00:09.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xde00. Vers LK1.1.18
eth0: Dropping NETIF_F_SG since no checksum feature.
PCI: Found IRQ 10 for device 00:0a.0
00:0a.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xdc00. Vers LK1.1.18
eth1: Dropping NETIF_F_SG since no checksum feature.
PCI: Found IRQ 11 for device 00:0b.0
PCI: Sharing IRQ 11 with 00:07.2
00:0b.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xda00. Vers LK1.1.18
eth2: Dropping NETIF_F_SG since no checksum feature.
XFS mounting filesystem ide0(3,5)
Ending clean XFS mount for filesystem: ide0(3,5)
XFS mounting filesystem ide0(3,6)
Ending clean XFS mount for filesystem: ide0(3,6)
XFS mounting filesystem ide0(3,7)
Ending clean XFS mount for filesystem: ide0(3,7)
XFS mounting filesystem ide0(3,8)
Ending clean XFS mount for filesystem: ide0(3,8)

eth1: Setting full-duplex based on MII #24 link partner capability of
01e1.
eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
IPSEC EVENT: KLIPS device ipsec0 shut down.


eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
IPSEC EVENT: KLIPS device ipsec0 shut down.


klips_error:ipsec_xmit_send: ip_send() failed, err=1
eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
IPSEC EVENT: KLIPS device ipsec0 shut down.


IPSEC EVENT: KLIPS device ipsec0 shut down.


eth0: Setting promiscuous mode.
device eth0 entered promiscuous mode
device eth0 left promiscuous mode
eth2: Setting promiscuous mode.
device eth2 entered promiscuous mode
device eth2 left promiscuous mode

This morning:

IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.

This is from syslog:

May 4 07:12:23 Pleiadi ipsec__plutorun: /usr/local/lib/ipsec/_plutorun:
line 221: 18782 Aborted (core dumped)
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
May 4 07:12:23 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
May 4 07:12:23 Pleiadi ipsec__plutorun: restarting IPsec after pause...
May 4 07:12:34 Pleiadi kernel: IPSEC EVENT: KLIPS device ipsec0 shut
down.
May 4 07:12:35 Pleiadi ipsec_setup: ...Openswan IPsec stopped
May 4 07:12:35 Pleiadi ipsec_setup: Stopping Openswan IPsec...
May 4 07:12:35 Pleiadi ipsec_setup: Removing orphaned
/var/run/pluto/pluto.pid:
May 4 07:12:35 Pleiadi ipsec_setup:
/usr/local/libexec/ipsec/klipsdebug: pfkey write failed, tried to write
72 octets, returning -1 with errno=28.
May 4 07:12:35 Pleiadi ipsec_setup: no room in kernel SAref table.
Cannot process request.
May 4 07:12:35 Pleiadi ipsec_setup: /usr/local/libexec/ipsec/eroute:
pfkey write failed, returning -1 with errno=28.
May 4 07:12:35 Pleiadi ipsec_setup: no room in kernel SAref table.
Cannot process request.
May 4 07:12:35 Pleiadi ipsec_setup: /usr/local/libexec/ipsec/spi: pfkey
write failed (errno=28): no room in kernel SAref table. Cannot process
request.
May 4 07:12:35 Pleiadi ipsec_setup: KLIPS debug `none'
May 4 07:12:36 Pleiadi ipsec_setup: KLIPS ipsec0 on eth0
x.x.x.x/y.y.y.y broadcast x.x.x.x
May 4 07:12:36 Pleiadi ipsec_setup: ...Openswan IPsec started
May 4 07:12:36 Pleiadi ipsec_setup: Restarting Openswan IPsec 2.3.1...
May 4 07:12:36 Pleiadi ipsec_setup:
/usr/local/libexec/ipsec/klipsdebug: pfkey write failed, tried to write
72 octets, returning -1 with errno=28.
May 4 07:12:36 Pleiadi ipsec_setup: no room in kernel SAref table.
Cannot process request.
May 4 07:12:36 Pleiadi ipsec_setup: /usr/local/libexec/ipsec/eroute:
pfkey write failed, returning -1 with errno=28.
May 4 07:12:36 Pleiadi ipsec_setup: no room in kernel SAref table.
Cannot process request.
May 4 07:12:36 Pleiadi ipsec_setup: /usr/local/libexec/ipsec/spi: pfkey
write failed (errno=28): no room in kernel SAref table. Cannot process
request.
May 4 07:12:41 Pleiadi ipsec__plutorun: 003 ERROR: "napoli": pfkey
write() of SADB_X_ADDFLOW message 5 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:41 Pleiadi ipsec__plutorun: 025 "napoli": could not route
May 4 07:12:41 Pleiadi ipsec__plutorun: ...could not route conn
"napoli"
May 4 07:12:41 Pleiadi ipsec__plutorun: 003 ERROR: "noventa": pfkey
write() of SADB_X_ADDFLOW message 6 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:41 Pleiadi ipsec__plutorun: 025 "noventa": could not route
May 4 07:12:41 Pleiadi ipsec__plutorun: ...could not route conn
"noventa"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "roma": pfkey
write() of SADB_X_ADDFLOW message 7 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "roma": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn "roma"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "bst-mobile": pfkey
write() of SADB_X_ADDFLOW message 8 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "bst-mobile": could not
route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"bst-mobile"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "bst-piacenza":
pfkey write() of SADB_X_ADDFLOW message 9 for flow %trap failed. Errno
28: No space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "bst-piacenza": could not
route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"bst-piacenza"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "guanzate": pfkey
write() of SADB_X_ADDFLOW message 10 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "guanzate": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"guanzate"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "cernusco": pfkey
write() of SADB_X_ADDFLOW message 11 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "cernusco": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"cernusco"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "eridania": pfkey
write() of SADB_X_ADDFLOW message 12 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "eridania": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"eridania"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "sico": pfkey
write() of SADB_X_ADDFLOW message 13 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "sico": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn "sico"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "firenze": pfkey
write() of SADB_X_ADDFLOW message 14 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "firenze": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"firenze"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "bst-bologna": pfkey
write() of SADB_X_ADDFLOW message 15 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "bst-bologna": could not
route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"bst-bologna"
May 4 07:12:42 Pleiadi ipsec__plutorun: 003 ERROR: "genova": pfkey
write() of SADB_X_ADDFLOW message 16 for flow %trap failed. Errno 28: No
space left on device
May 4 07:12:42 Pleiadi ipsec__plutorun: 025 "genova": could not route
May 4 07:12:42 Pleiadi ipsec__plutorun: ...could not route conn
"genova"
May 4 07:12:43 Pleiadi ipsec__plutorun: 104 "napoli" #1: STATE_MAIN_I1:
initiate
May 4 07:12:43 Pleiadi ipsec__plutorun: ...could not start conn
"napoli"
May 4 07:12:43 Pleiadi ipsec__plutorun: 104 "noventa" #2:
STATE_MAIN_I1: initiate
May 4 07:12:43 Pleiadi ipsec__plutorun: ...could not start conn
"noventa"
May 4 07:12:43 Pleiadi ipsec__plutorun: 104 "roma" #3: STATE_MAIN_I1:
initiate
May 4 07:12:43 Pleiadi ipsec__plutorun: ...could not start conn "roma"
May 4 07:12:43 Pleiadi ipsec__plutorun: 104 "bst-mobile" #4:
STATE_MAIN_I1: initiate
May 4 07:12:43 Pleiadi ipsec__plutorun: ...could not start conn
"bst-mobile"
May 4 07:12:44 Pleiadi ipsec__plutorun: 104 "guanzate" #6:
STATE_MAIN_I1: initiate
May 4 07:12:44 Pleiadi ipsec__plutorun: ...could not start conn
"guanzate"
May 4 07:12:44 Pleiadi ipsec__plutorun: 104 "cernusco" #8:
STATE_MAIN_I1: initiate
May 4 07:12:44 Pleiadi ipsec__plutorun: ...could not start conn
"cernusco"
May 4 07:12:44 Pleiadi ipsec__plutorun: 104 "eridania" #9:
STATE_MAIN_I1: initiate
May 4 07:12:44 Pleiadi ipsec__plutorun: ...could not start conn
"eridania"
May 4 07:12:45 Pleiadi ipsec__plutorun: 104 "sico" #12: STATE_MAIN_I1:
initiate
May 4 07:12:45 Pleiadi ipsec__plutorun: ...could not start conn "sico"
May 4 07:12:45 Pleiadi ipsec__plutorun: 104 "firenze" #15:
STATE_MAIN_I1: initiate
May 4 07:12:45 Pleiadi ipsec__plutorun: ...could not start conn
"firenze"
May 4 07:12:45 Pleiadi ipsec__plutorun: 104 "bst-bologna" #18:
STATE_MAIN_I1: initiate
May 4 07:12:45 Pleiadi ipsec__plutorun: ...could not start conn
"bst-bologna"
May 4 07:12:46 Pleiadi ipsec__plutorun: 104 "genova" #19:
STATE_MAIN_I1: initiate
May 4 07:12:46 Pleiadi ipsec__plutorun: ...could not start conn
"genova"
May 4 07:13:23 Pleiadi ipsec__plutorun: /usr/local/lib/ipsec/_plutorun:
line 221: 5953 Aborted (core dumped)
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
May 4 07:13:23 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
May 4 07:13:23 Pleiadi ipsec__plutorun: restarting IPsec after pause...
May 4 07:13:34 Pleiadi kernel: IPSEC EVENT: KLIPS device ipsec0 shut
down.
May 4 07:13:34 Pleiadi ipsec_setup: ...Openswan IPsec stopped
May 4 07:13:34 Pleiadi ipsec_setup: Stopping Openswan IPsec...

This is the output from gdb --core=core

GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i486-slackware-linux".
Core was generated by
`/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipse'.
Program terminated with signal 6, Aborted.
#0 0x40082ef1 in ?? ()
(gdb) quit
Post by Paul Wouters
Post by Marco Berizzi
I'm running OpenSWAN 2.3.1 on Slackware 10.1
I have manually patched (make kpatch) linux
vanilla 2.4.30
Gcc is 3.3.5, glibc 2.3.4
Today, after about 10 uptime days pluto has
been crashed.
ip_send()
Post by Paul Wouters
Post by Marco Berizzi
failed, err=1
line 221: 8417 Aborted
/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-none --uniqueids
Apr 26 16:24:32 Pleiadi ipsec__plutorun: !pluto failure!: exited with
error status 134 (signal 6)
Please add dumpdir=/tmp to config setup and restart openswan. When the
failire happens again, you should have a core file. Use gdb on it to give
us a backtrace.
Paul
Paul Wouters
2005-05-06 11:53:26 UTC
Permalink
Post by Marco Berizzi
#ipsec setup start
ipsec_setup: Starting Openswan IPsec 2.3.1...
ipsec_setup: /usr/local/libexec/ipsec/klipsdebug: pfkey write failed,
tried to write 72 octets, returning -1 with errno=28.
ipsec_setup: no room in kernel SAref table. Cannot process request.
ipsec_setup: /usr/local/libexec/ipsec/eroute: pfkey write failed,
returning -1 with errno=28.
ipsec_setup: no room in kernel SAref table. Cannot process request.
ipsec_setup: /usr/local/libexec/ipsec/spi: pfkey write failed
(errno=28): no room in kernel SAref table. Cannot process request.
klips_error:ipsec_xmit_send: ip_send() failed, err=1
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
IPSEC EVENT: KLIPS device ipsec0 shut down.
line 221: 18782 Aborted (core dumped)
Can you add dumpdir=/tmp in ipsec.conf's config setup section, and produce
a core file and run gdb on it to get a backtrace?

Thanks,

Paul
Marco Berizzi
2005-05-06 12:23:12 UTC
Permalink
Post by Paul Wouters
Can you add dumpdir=/tmp in ipsec.conf's config setup section, and produce
a core file and run gdb on it to get a backtrace?
Here is.


GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "i486-slackware-linux"...Using host
libthread_db library "/lib/libthread_db.so.1".

Core was generated by
`/usr/local/libexec/ipsec/pluto --nofork --secretsfile
/etc/ipsec.secrets --ipse'.
Program terminated with signal 6, Aborted.
#0 0x40082ef1 in ?? ()
(gdb) bt
#0 0x40082ef1 in ?? ()
#1 0x40082b15 in ?? ()
#2 0x00007e83 in ?? ()
#3 0x00000006 in ?? ()
#4 0x40172ff4 in ?? ()
#5 0x08109138 in ?? ()
#6 0xbffff328 in ?? ()
#7 0x400843fd in ?? ()
#8 0x00000006 in ?? ()
#9 0xbffff210 in ?? ()
#10 0x00000000 in ?? ()
#11 0x00000020 in ?? ()
#12 0x00000000 in ?? ()
#13 0x00000000 in ?? ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000000 in ?? ()
#25 0x00000000 in ?? ()
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x00000000 in ?? ()
#42 0x00000000 in ?? ()
#43 0x400600b0 in ?? ()
#44 0x40059000 in ?? ()
#45 0xbffff2b0 in ?? ()
#46 0x08100f38 in ?? ()
#47 0x400bc614 in ?? ()
#48 0x00000000 in ?? ()
#49 0x00000000 in ?? ()
#50 0x00000000 in ?? ()
#51 0x00000000 in ?? ()
#52 0x080e9380 in ipv6_all ()
#53 0x40174a0c in ?? ()
#54 0x08109138 in ?? ()
#55 0x08109138 in ?? ()
#56 0xbffff4c0 in ?? ()
#57 0x40015ff8 in ?? ()
#58 0x00000001 in ?? ()
#59 0x400164d0 in ?? ()
#60 0xbffff310 in ?? ()
#61 0x4000a269 in ?? ()
#62 0x4001667c in ?? ()
#63 0x40059308 in ?? ()
#64 0x00000001 in ?? ()
#65 0x00000001 in ?? ()
#66 0x00000000 in ?? ()
#67 0x08048ac0 in ?? ()
#68 0x080e4214 in ?? ()
#69 0x0000004b in ?? ()
#70 0x08049386 in ?? ()
#71 0x400600b0 in ?? ()
#72 0x08109138 in ?? ()
#73 0x08109138 in ?? ()
#74 0xbffff4c0 in ?? ()
#75 0xbffff338 in ?? ()
#76 0x4000a440 in ?? ()
#77 0x00000000 in ?? ()
#78 0x401749c0 in ?? ()
#79 0x08109138 in ?? ()
#80 0xbffff4c0 in ?? ()
#81 0xbffff338 in ?? ()
#82 0x08056da3 in passert_fail (
pred_str=0x6 <Error reading address 0x6: No such file or directory>,
file_str=0xbffff210 " ", line_no=0) at log.c:598
Previous frame inner to this frame (corrupt stack?)
(gdb) quit

Loading...