Am Samstag 10 Juli 2010, 10:40:52 schrieb Sven Eckelmann:
Daniel Seither wrote:
Am 10.07.2010 01:07, Sven Eckelmann wrote:
batman-adv works quite well for us - but that doesn't mean that it is good in context of the current kernel development. And who should know it better than the netdev guys.
Hagen Paul Pfeifer suggested in his message "a generalized architecture and a user space implementation of the protocol". What came to my mind when I read this again was a division of control plane and data/forwarding plane as known from traditional routing.
The whole forwarding stuff would stay in the kernel, using a simple routing table (for destination X, send to node Y on interface Z).
This would go against the bonding/alternating functionality.
The bonding/alternating functionality could be part of the routing framework. I think there is something similar on IP layer routing in linux.
(a framework like this would make it very easy to port additional routing daemons for layer 2 routing, I already hear the 802.11s group crying because of competitors ;) ).
Henning Rogge