From: "\"Juha Ylönen\"" <ylonen@gmx.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] batman-adv on different archs
Date: Mon, 18 Jan 2010 12:27:06 +0100 [thread overview]
Message-ID: <20100118112706.91160@gmx.net> (raw)
Hi,
I've been trying to get my embedded project included in my mesh, but no success yet. Could anyone give a pointers what is going wrong?
I have batman-adv compiled on my laptop, and also for testing purposes on another laptop, they see each other and everything is fine. I used the same sources and compiled it cleanly on each.
The problem comes when I try to add my little ARM based linux box onto the group. Again same sources used (latest stable from the wiki), crosscompiles fine and I can load the module as normal on the box. Setup goes as it should on both the device and the laptop, and both systems seems to be running smoothly. But my laptop can only see the other laptop, and the device doesn't see anyone. The wireless net is working and I can ping each device directly if I assign IP's to the 'real' interfaces, but through bat0 nothing is found. Any idea what is going wrong?
---
I've also played with the batman daemon on the device, with it I the laptop and device can see each other just fine. The problem there is that apparently it doesn't really support multicast forwarding? i.e. If I have 3 devices A-B-C, where A does not have direct link to C (batman routes through B), sending a multicast from A can be received in B and vice versa, also same for C-B, but no messages from A to C. Will I have the same problem with batman-adv? Or can this be fixed on the daemon?
Best Regards
Juha
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
next reply other threads:[~2010-01-18 11:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 11:27 "Juha Ylönen" [this message]
2010-01-18 11:39 ` [B.A.T.M.A.N.] batman-adv on different archs Andrew Lunn
2010-01-18 13:29 ` "Juha Ylönen"
2010-01-18 13:38 ` Marek Lindner
2010-01-18 13:51 ` Andrew Lunn
2010-01-19 7:46 ` "Juha Ylönen"
2010-01-19 7:43 ` "Juha Ylönen"
2010-01-19 12:07 ` Marek Lindner
2010-01-19 14:51 ` "Juha Ylönen"
2010-01-19 15:11 ` Sven Eckelmann
[not found] ` <20100119153233.319500@gmx.net>
2010-01-19 17:12 ` Sven Eckelmann
2010-01-19 19:37 ` Simon Wunderlich
2010-01-20 14:05 ` "Juha Ylönen"
2010-01-20 21:58 ` Marek Lindner
2010-01-18 11:42 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 14:58 "Juha Ylönen"
2010-01-20 2:15 ` Marek Lindner
2010-01-20 9:29 ` "Juha Ylönen"
2010-01-20 9:42 ` Marek Lindner
2010-01-20 9:49 ` Andrew Lunn
2010-01-20 9:51 ` Sven Eckelmann
2010-01-20 13:12 ` "Juha Ylönen"
2010-01-20 22:32 ` Marek Lindner
2010-01-21 14:12 ` "Juha Ylönen"
2010-01-21 15:29 ` Sven Eckelmann
2010-01-21 17:17 ` Gus Wirth
2010-01-21 18:32 ` Sven Eckelmann
2010-01-22 18:26 ` Simon Wunderlich
2010-01-24 21:19 ` "Juha Ylönen"
2010-01-21 19:02 "Juha Ylönen"
2010-01-22 12:16 ` Sven Eckelmann
2010-01-24 21:17 "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann
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=20100118112706.91160@gmx.net \
--to=ylonen@gmx.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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