Hi!
I have a feature request.
On Fri, Apr 13, 2012 at 7:59 AM, Andrew Lunn andrew@lunn.ch wrote:
- BATMAN is not a daemon. Its a kernel module. Hence it cannot play
around with routes, even if it wanted to. Also, adding/removing routes is policy, and the Linux/Unix view of the world is that user space is responsible for deciding policy.
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. :-)
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.
I like the idea because it allows general hooks into Batman reachability awareness. So no duplication of this is necessary. Also, Batman already exchanges information, so we could just allow custom additional information from nodes to be exchanged. Maybe even stored in that DHT you have.
Mitar