From: fboehm <fboehm@aon.at>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] Linux bridge-code for something like BATMAN
Date: Wed, 15 Jun 2011 21:05:26 +0200 [thread overview]
Message-ID: <4DF90276.8050701@aon.at> (raw)
Hi,
I know bridging is not routing but I was thinking since some time if it
is possible to modify the linux bridge-code for forwarding layer2
packets according to the rules of some routing algorithm. This means the
bridge would not learn mac addresses from ARP protocol any longer but
from a daemon. The result would be a layer2 mesh routing like BATMAN does.
OLSR is doing quite the same one layer above by manipulating the routing
table with the OLSR daemon. Of course it's much easier to manipulate a
routing table because there are interfaces for doing this.
It's just an idea and I would like to hear your expert opinions.
Kind regards,
Franz
next reply other threads:[~2011-06-15 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 19:05 fboehm [this message]
2011-06-15 19:22 ` [B.A.T.M.A.N.] Linux bridge-code for something like BATMAN Marek Lindner
2011-06-15 19:28 ` fboehm
2011-06-15 20:23 ` 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=4DF90276.8050701@aon.at \
--to=fboehm@aon.at \
--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