From: Predrag Balorda <predrag.balorda@gmail.com>
To: 'The list for a Better Approach To Mobile Ad-hoc Networking'
<b.a.t.m.a.n@open-mesh.net>
Subject: RE: [B.A.T.M.A.N.] strange batman aborting
Date: Thu, 6 Dec 2007 12:08:43 +0100 [thread overview]
Message-ID: <000c01c837f8$5ed76290$1c8627b0$@com> (raw)
In-Reply-To: <20071206023407.GA4041@apoderado.ometepe.net>
This table full thingy could be that you are reaching your upper limit on
connections. Perhaps someone playing with bittorrent (or similar) on your
network? You either increase the maximum number of connections or you
decrease the timeout values.
Just an idea...
Pele
-----Original Message-----
From: b.a.t.m.a.n-bounces@open-mesh.net
[mailto:b.a.t.m.a.n-bounces@open-mesh.net] On Behalf Of Jan Hetges
Sent: Thursday, December 06, 2007 3:34 AM
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] strange batman aborting
Hi All
after two weeks uptime bmxd_rv804 just died! and not only that one, but on a
neighbouring node (~5 days uptime) as well.
So i restarted them, and about 26hrs later, they are both dead again.
So i enabled Lui's watchout4batman, maybe i see at least, which one dies
first. Only unnormal in the log:
user.warn kernel: nf_conntrack: table full, dropping packet.
any ideas?
cheers
--Jan
p.s. both boxes run kamikaze 7.07 i386
next prev parent reply other threads:[~2007-12-06 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 2:34 [B.A.T.M.A.N.] strange batman aborting Jan Hetges
2007-12-06 4:34 ` Axel Neumann
2007-12-06 11:08 ` Predrag Balorda [this message]
2007-12-06 23:42 ` Jan Hetges
2007-12-06 17:48 ` tetzlav
2007-12-06 20:31 ` Jan Hetges
2007-12-10 8:50 ` [B.A.T.M.A.N.] exp-rv811 and exp-864 non-interoperable? Predrag Balorda
2007-12-10 20:50 ` Jan Hetges
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='000c01c837f8$5ed76290$1c8627b0$@com' \
--to=predrag.balorda@gmail.com \
--cc=b.a.t.m.a.n@open-mesh.net \
--cc=pele@balorda.com \
/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