From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Migration to Batman
Date: Mon, 16 Apr 2012 12:37:36 +0200 [thread overview]
Message-ID: <201204161237.37008.lindner_marek@yahoo.de> (raw)
In-Reply-To: <CAKLmikPJBmk=Xoom0a1D2OFfx6o8OtSk7D4PdT3TDXDx9iyO1A@mail.gmail.com>
On Monday, April 16, 2012 12:25:42 Mitar wrote:
> I have problems with an idea of running another routing protocol on
> top of Batman. I think this is creates unnecessary additional
> bandwidth consumption:
> 1) routing protocol has to find which nodes are reachable
> 2) routing protocol has to exchange information about announced routes
>
> But 1) Batman already knows. So we could have a netlink protocol where
> user-land daemon could subscribe to events and get for example two
> events: "node reachable" and "node unreachable". Then it can do some
> user-land mingling. :-)
Batman-adv already has an event reporting system (via sysfs):
http://www.open-mesh.org/wiki/batman-adv/Uevent
It could be easily extended to also throw node events (reachable/unreachable).
Note: Whoever is going to implement that should think about the implications
of mesh clouds periodically connecting and disconnecting. A lot of events
could be fired over and over again.
> And for 2), Batman could allow a general key/value additional
> information to be announced by nodes. From its point of view that
> information can be anything.
>
> And the in our case we could add to each node information which IP it
> has and which subnets it has behind. This information would then be
> announced to other nodes. And then we could run a simple daemon on
> other nodes which would listen to netlink events and once a node is
> reachable, read that information and setup necessary routes.
There is no need to implement such a thing in batman-adv. You can have this
feature today by using any broadcast system (avahi, routing daemon, self-
implemented thingy, etc) you like. Here also lies the misunderstanding: You
don't need to run another routing protocol "on top" of batman-adv. You only
run it to announce "stuff". You can simply run your routing protocol of choice
to announce the routes.
This was explained several times in this thread - maybe it still is not clear?
Cheers,
Marek
next prev parent reply other threads:[~2012-04-16 10:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 10:26 [B.A.T.M.A.N.] Migration to Batman Mitar
2012-04-12 10:36 ` Gioacchino Mazzurco
2012-04-12 12:00 ` Antonio Quartulli
2012-04-12 15:13 ` Mitar
2012-04-12 15:36 ` Andrew Lunn
2012-04-12 17:12 ` Mitar
2012-04-12 18:12 ` Andrew Lunn
2012-04-12 19:49 ` 3zl Trizonelabs
[not found] ` <CAOaDhSRTgejL5tzAnAx6wBso1sjWn_7bVuT6P1_C1qcVu25McQ@mail.gmail.com>
2012-04-12 15:37 ` Jernej Kos
2012-04-12 17:19 ` Mitar
2012-04-12 21:08 ` Mitar
2012-04-12 21:15 ` Gioacchino Mazzurco
2012-04-13 5:59 ` Andrew Lunn
2012-04-13 7:58 ` Mitar
2012-04-13 8:15 ` Andrew Lunn
2012-04-13 8:41 ` Mitar
2012-04-13 9:24 ` Andrew Lunn
2012-04-13 13:24 ` Mitar
2012-04-14 2:26 ` Nicolás Echániz
2012-04-14 9:06 ` Mitar
2012-04-16 10:25 ` Mitar
2012-04-16 10:37 ` Marek Lindner [this message]
2012-04-16 10:46 ` Mitar
2012-04-16 10:58 ` Marek Lindner
2012-04-16 12:32 ` Mitar
2012-04-16 12:40 ` Antonio Quartulli
2012-04-16 13:59 ` Mitar
2012-04-16 18:28 ` Marek Lindner
2012-04-16 18:30 ` Marek Lindner
2012-04-16 11:03 ` Antonio Quartulli
2012-04-16 12:37 ` Mitar
2012-04-12 17:10 ` Mitar
2012-04-12 22:13 ` Marek Lindner
2012-04-12 17:05 ` Mitar
2012-04-12 22:17 ` Marek Lindner
2012-04-13 6:22 ` Antonio Quartulli
2012-04-13 7:29 ` Mitar
2012-04-13 7:43 ` Andrew Lunn
2012-04-13 7:51 ` Mitar
2012-04-13 8:26 ` Andrew Lunn
2012-04-13 8:35 ` Mitar
2012-04-13 8:52 ` Christian Huldt
2012-04-13 13:32 ` Mitar
2012-04-13 13:50 ` Andrew Lunn
2012-04-13 13:53 ` Mitar
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=201204161237.37008.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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