From: Jan Hetges <tran@ms20.net>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] batmand-exp test in the developing world
Date: Thu, 1 Nov 2007 23:17:12 -0600 [thread overview]
Message-ID: <20071102051711.GA8869@apoderado.ometepe.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2466 bytes --]
Hola todos
after
On Mon, Oct 15, 2007 at 04:14:36PM +0200, elektra wrote:
> I'm sorry to say that 0.3beta is not usable at the moment.
and my tests with 0.3-beta_~rv720 showed path-detection pretty
broken, i tried exp-0.3. Finally i installed rv772 on 14
nodes real-world, rural nicaragua "non-profit-WISP/community
network" parallel to existing olsrd(0.4.10/0.5.2/0.5.4pre)/
batmand_0.2-rv502.
the solar powered nodes run bmxd-rv772 for almost 36hrs
now, with no significant instabilities(with lots of tunneled
download-traffic, the tunnel get's a bit unstable, what Axel already
fixed in rv774). CPU-usage on client nodes looks less than in
batmand_0.2, and slightly more than olsrd (would be interesting to
see that scaling in a cloud with >100 nodes (how's the
"massive parallel vm simulation" going btw?)), but is significantly
higher (about factor 2) on gateway node. Best path-detection and
usability/stability of routes so far. All nodes seem visible
everywhere anytime, which is the case in olsrd as well, but not in
batmand_0.2. I'm located two hops from the GW where my server also is.
So i'm streaming music from there to check the stability of the
route: with only olsrd it gets silent (with 1024KB disk cache
in mplayer, ~40sec) pretty regularly (because of "collapsing
routing tables" somewhere), with only batmand_0.2 it's even worse
(because the GW node "doesn't hear my OGMs" too well). Both together
are pretty usable. So i tried with only bmxd and disk cache set
to 32KB (>1.5sec) and in tree hours music stopped once for <2sec !
from the "user-feeling" it's the way best mesh-daemon i tried so far.
for fairness i have to say that my olsrds are neither all up to date,
nor pretty well configured, but i beleave olsrd is a
"historically crippled design" and the evolution of batmand will
show the possibilities of wireless mesh networking.
this all needs some further testing and improvements, but
i'm pretty sure all the good bits will find their way into 0.3-final.
Thanks to Elektra, Marek, Axel and everyone else who put so much
energy into this amazing peace of free software.
BatMan-eXperimental 0.3-alpha rv772 (compatibility version 5)
/' '\
/ \__^..^__/ \
/ / _ \vv/ _ \ \
/ \/ \
/ \
May the bat guide your path ...
cheers
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-11-02 5:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 5:17 Jan Hetges [this message]
2007-11-03 21:39 ` [B.A.T.M.A.N.] batmand-exp test in the developing world Aaron Kaplan
2007-11-04 1:19 ` elektra
-- strict thread matches above, loose matches on Subject: below --
2007-11-04 0:53 AW: " Marek Lindner
2007-11-04 1:10 ` Jan Hetges
2007-11-04 2:36 ` elektra
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=20071102051711.GA8869@apoderado.ometepe.net \
--to=tran@ms20.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.