Re: [B.A.T.M.A.N.] Problems to add Batman-adv in wlan0 Nanostation M5

[Sven Eckelmann <sven@narfation.org>]

[-- Attachment #1: Type: text/plain, Size: 3939 bytes --]

On Tuesday 31 July 2012 11:41:15 Esteban Municio wrote:
> Hi all
> 
> I`m working on a academic develop project for improve the networks in
> rural areas in Peru. We are doing some test with 6 Nanostation M5 for
> create a mesh network.
> 
> I tried Commotion software with OLSR and all was Ok. Now, we are
> testing BATMAN, with OpenWRT and batman-adv module, but I have some
> problems.
> 
> I have compiled OpenWrt Backfire r32751 (Load: 0.09 0.10 0.05) and
> installed batman-adv with opkg following this
> http://wiki.openwrt.org/inbox/mesh.batman

Why are you installing it with opkg? This sounds a little bit like you try to
load a kernel module that wasn't compiled for the kernel that is running on
the machine (which would be extreme bad when there are ABI differences). Also
this "pizza" link you showed at the bottom of the mail gives the impression
that you may have done something like that.

The best way is to include it in your image.

> When I put:
> lsmod | grep batman
> I get
> batman_adv             67936  0
> 
> and seems to be load in the kernel
> 
> But when I try to add the interface wlan0 for activate batman in it,
> the Nanostation remains locked and i need to reboot.
> I have tried this with:
> 
> echo bat0 > /sys/class/net/wlan0/batman_adv/mesh_iface
> 
> and
> 
> batctl if add wlan0
> 
> with the same bad result.
> What am i doing wrong?

Hard to tell with the information we got here. Are you using the serial console
on your device? Does it print a backtrace (can you create a backtrace with
symbol tables enabled)? Are you sure that the kernel and batman-adv module are
100% binary compatible? What version of batman-adv is it? Did you try the
newest openwrt devel package from
 http://downloads.open-mesh.org/svn/openwrt-feed/ (i think the package is
called kmod-batman-adv-devel)?

batctl: acd06db051419d3b323675ab2d7c897f2a5efc2a
batman-adv: 3fdeaa6bfb404311b73a689e984672161403a0c2

[...]
> I have noticed that i have not the bat0 interface created,is it normal?
> Do i need create another aditional interface like ath0?

bat0 (or any other name you choose for your batman-adv device(s)) are created
after you attach an interface to it (this is what you are doing when you say
that your node "freezes").

> I have been following that manuals:
> http://pizza.hskflashcards.com/index.php?page=B.A.T.M.A.N.+Advanced+on+OpenW
> rt+How-To

Uh, please don't use this one. It is outdated as hell and has nearly nothing
to do with the stuff you are using (or at least should use).

> Do you recomend me to change to batmand instead?

Just to give an impression:

Latest release of batmand:
 http://git.open-mesh.org/batmand.git/commit/3aeebaf87974a069278a3feee31345da664fc090

Latest release of batman-adv
 http://git.open-mesh.org/batman-adv.git/commit/b82d11e243ec144c515e7d04e8e8c31b111a060d

Commits in batmand in the last 6 months (master branch): 0
Commits in batman-adv in the last 6 months (master branch): ~250 (and this does
not include all the stuff that happens before a change is accepted)

Of course, this can also be a sign of perfection. But I can say for sure that
the most development in the last two years happened in batman-adv and not in
batmand.

> Do you know if there is any BATMAN implementation for a mesh network
> of Nanostation M5, easier to install and manipulate?

Um, even easier? At least I find it extreme easy to get it running:

$ modprobe batman-adv
$ batctl -m bat4 interface add eth0
$ ip addr add 192.168.3.11/24 dev bat4
$ ip link set dev bat4 up
$ batctl -m bat4 originators

And only step 1 and 2 are batman-adv relevant. The rest is just to configure the
usual stuff and step 5 to check for detected originators. And "-m bat4" is
optional. I just wanted to call my device bat4. Please let me know how this can
be made easier without restricting users.

And why are you refering to a specific product? I thought that you just use
OpenWRT.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]