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 mujlticast [WAS: Re: batman-adv on different archs]
Date: Tue, 26 Jan 2010 08:20:58 +0100 [thread overview]
Message-ID: <20100126072058.181620@gmx.net> (raw)
In-Reply-To: <201001242303.56730.sven.eckelmann@gmx.de>
-------- Original-Nachricht --------
> Datum: Sun, 24 Jan 2010 23:03:48 +0100
> Von: Sven Eckelmann <sven.eckelmann@gmx.de>
>
> Ok, so we have a real simple example here. We see that we have a "large"
> ethernet frame (unlike batman-adv) and a "unnormal" ethernet type. So
> maybe
> you could forward rawsend.log and rawsend.c to the driver developers. They
> should be able to find and fix the problem with such a real small example.
> Or
> does anyone see a related problem in rawsend.c?
Thanks for the analysis, I'll try to get this solved with the driver.
> What is the batmand stuff for?
I'm evaluating the batmand for routing multicast audiostream in a mesh. Batmand seems to be doing the routing better than olsr, but the lack of multicast is a problem, hence batman-adv.
I tried batman-adv and multicast routing with couple of laptops, but it did not work quite well. Some packages seemed to be left ping-ponging in the mesh, while others disappeared completely. Is batman-adv multicast being actively used somewhere?
-Juha
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
next prev parent reply other threads:[~2010-01-26 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:17 [B.A.T.M.A.N.] batman-adv on different archs "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann
2010-01-26 7:20 ` "Juha Ylönen" [this message]
2010-01-26 7:24 ` [B.A.T.M.A.N.] batman-adv mujlticast [WAS: Re: batman-adv on different archs] 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=20100126072058.181620@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