From: Marek Lindner <lindner_marek@yahoo.de>
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.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)
Date: Tue, 24 Mar 2009 01:13:32 +0800 [thread overview]
Message-ID: <200903240116.07288.lindner_marek@yahoo.de> (raw)
In-Reply-To: <3ebdcf0a0903210607v5346dfbn7bb2e1f5bce854b4@mail.gmail.com>
Hi,
> In such a meshbox, I installed OpenWRT Kamikaze 8.09.
> In order to do that, I downloaded the OpenWRT trunk and all the
> available packages from the OpenWRT repository.
> Then, I built the image selecting all the interesting packages; among
> these packages, in the network section,
> I selected batmand (B.A.T.M.A.N. 3 routing daemon).
> By the way, I did not compile batman by myself but it was directly
> integrated in the Kamikaze image.
I downloaded the OpenWRT trunk and compiled the i386 image before loading it
into a qemu environment. I can confirm that batman does nothing if started
without a debug level. It seems the main thread is not doing anything.
Interestingly, if I compile & run batman on my debian machine it runs without
problems. I guess OpenWRT uses some different libs / compile time options / etc
that provoke that problem.
As a short term workaround I suggest you start batman with a debug level and
redirect the output:
batmand -d 3 wlan0 > /dev/null 2>&1
I will try to debug this during the coming days but can't promise anything as
I'm looking for the needle in the haystack.
Regards,
Marek
next prev parent reply other threads:[~2009-03-23 17:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 14:43 [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) Max
2009-03-19 2:55 ` Marek Lindner
2009-03-19 13:38 ` Max
2009-03-20 12:47 ` Marek Lindner
2009-03-20 13:03 ` Max
2009-03-21 1:13 ` Marek Lindner
2009-03-21 13:07 ` Max
2009-03-23 17:13 ` Marek Lindner [this message]
2009-03-23 22:05 ` Sven Eckelmann
2009-03-24 19:17 ` Sven Eckelmann
2009-03-25 2:44 ` Marek Lindner
2009-03-26 12:59 ` [B.A.T.M.A.N.] [PATCH] Don't detach batmand to background by default Sven Eckelmann
2009-03-31 18:26 ` Marek Lindner
2009-04-01 10:28 ` Sven Eckelmann
2009-04-01 10:31 ` [B.A.T.M.A.N.] [PATCH 1/2] Add parameter to disable fork to background Sven Eckelmann
2009-04-01 10:31 ` [B.A.T.M.A.N.] [PATCH 2/2] Sanitise batmand process by reexecuting it Sven Eckelmann
2009-04-01 22:20 ` [B.A.T.M.A.N.] [PATCHv2 " Sven Eckelmann
2009-03-24 12:45 ` [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) P. Mazart
2009-04-11 0:54 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2009-03-19 12:55 Marco Tozzini
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=200903240116.07288.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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