From: "Linus Lüssing" <linus.luessing@web.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] Make batman-adv a multicast-aware layer 2 switch
Date: Thu, 28 May 2009 01:28:11 +0200 [thread overview]
Message-ID: <20090527232811.GA4848@Linus-Debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Yesterday, we (Marek, Julian, Linus) had some thoughts about the
advantages of having a multicast-aware BATMAN-Adv. Also some first
ideas about the actual implementation in BATMAN-Adv, which is not
a trivial task, have been discussed. The results so far and the
irc-log can be found in our wiki from the Lübeck-Freifunk
(http://luebeck.freifunk.net) in the section
Network->BATMAN-Adv-Multicast-Development. We definetly want to
push this feature further as it is especially very useful in
Mesh-networks and would like to hear from any other ideas of how
to implement this in the most efficient way and if there are any
concerns about the ideas for implementation yet. Also a
trac-enhancement-ticket can be found here:
http://www.open-mesh.net/ticket/128
Sincerely,
Julian, Linus - MetaMeute
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
reply other threads:[~2009-05-27 23:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090527232811.GA4848@Linus-Debian \
--to=linus.luessing@web.de \
--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