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.] Batman never stabilizes a route for nodes
Date: Fri, 12 Sep 2008 11:49:43 +0800 [thread overview]
Message-ID: <200809121149.43323.lindner_marek@yahoo.de> (raw)
In-Reply-To: <5635aa0d0809112012v1fbb67c4h663bf4fe4f063910@mail.gmail.com>
On Friday, 12. September 2008 11:12:21 Outback Dingo wrote:
> ok, im getting tcpdumps, this is a test bed of the same hardward atheros
> based Ubiquity NS2 devices running OpenWRT trunk
Then it is not related to your hw and the link posted earlier does not help
here.
> http://pastebin.com/md162302 which is from last night 10PM
Your log is pretty interesting. It shows that the basic functionality is there
but does not work reliably. The gateway is sending the keep alive reply to
the client which further indicates that we don't have an endianess issue
here.
> I also have 21 nodes, same hardware, running batgat which still crashed as
> Gustavo pointed out
> of which the logs were forwarded, the test bed has been setup to remove
> batgat and look for stability
Do you intend to test the latest stability patches from Sven ? May be it
solves your problem. It would be interesting to find out why the network is
less flaky if you use the module.
> im tcpdumping on both client and gateway now, ill forward the result of
> these logs in a bit
> as for wireshark ill make a build with that and see if i can get these logs
> also
Cool !
Greetings,
Marek
prev parent reply other threads:[~2008-09-12 3:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 13:01 [B.A.T.M.A.N.] Batman never stabilizes a route for nodes Outback Dingo
2008-09-12 2:31 ` Marek Lindner
2008-09-12 3:12 ` Outback Dingo
2008-09-12 3:49 ` Marek Lindner [this message]
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=200809121149.43323.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