From: Axel Neumann <axel@open-mesh.net>
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.] something about 0.3
Date: Thu, 6 Sep 2007 13:31:03 +0200 [thread overview]
Message-ID: <200709061331.03704.axel@open-mesh.net> (raw)
In-Reply-To: <26352.85.41.146.90.1189024539.squirrel@krisma.oltrelinux.com>
Hello Antonio,
On Mittwoch 05 September 2007, a.anselmi@oltrelinux.com wrote:
> I've downloaded and installed the 0.3 current for fonera-kamikaze platform
> and it seems work fine in a robin mesh cloud... but I've a problem which I
> don't well undestand.
> When batmand starts it ask me for a /dev/batman (a modul kernel) which
> would improve performance.
> I never read before about /dev/batman, so, anyone can suggest where I can
> find more documentation?
Well, we are currently sedulously working on improvements on the performance
of batman in the areas of cpu consumption and path detection. The kernel
module is an approach by Andreas and Marek to optimized cpu-load. You can
safely ignore this message because having the kernel module installed is not
mandatory. The idea is that if batman finds the kernel module it can be used
by the userspace batmand. IMHO (as in most open-source projects) the
documentation is always one step behind the latest development approaches.
Thats why its in the development and not in the stable stable folder.
> I believe that the originator messages compatibility number was been
> incremented in o.3 because a node running 0.2 doesn't see OGMs coming from
> batman o.3 nodes... is this correct?
Actually the compatibility number has not been increased with batmand-0.3_alpa
but the udp port number used by batman has changed.
Simon has managed to convience IANA to reserve a dedicated port for batman
which is now 4305 (see: http://www.iana.org/assignments/port-numbers )
( Just in case you downloaded batmand-exp_0.3, there the compatibility number
has been increased because it contains some experimental routing concepts
which are considered incompatible with the previous algorithm. Launch
$batmand -v to get some feedback about the running version and compatibility
number )
ciao,
axel
> Thanks
>
> --
> Antonio
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
next prev parent reply other threads:[~2007-09-06 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 20:35 [B.A.T.M.A.N.] something about 0.3 a.anselmi
2007-09-06 11:31 ` Axel Neumann [this message]
2007-09-06 13:10 ` a.anselmi
2007-09-06 13:54 ` Marek Lindner
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=200709061331.03704.axel@open-mesh.net \
--to=axel@open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox