Am 07.01.2010 um 22:14 schrieb Simon Wunderlich:
Hello,
we probably did not make this very clear in the document, but we will focus our work on batman-adv (layer 2) and will keep the batmand (layer 3) as it is for now. As a consequence, some ideas for BATMAN V are layer 2 exclusive (mesh bonding, incoming interface based routing).
thanks for that clarification.
On Thu, Jan 07, 2010 at 05:10:39PM +0100, Alex Morlang wrote:
Am 07.01.2010 um 14:23 schrieb Marek Lindner:
On Thursday 07 January 2010 15:44:36 Alex Morlang wrote:
are you considering attaching metrics to HNA?
That is not necessary as each non-batman host is connected to a batman host which has a metric. Therefore the implementation just needs to support the HNA metric. The batman daemon does so since quite a long time. It is on the feature list for batman-adv 0.3 but does not require any protocol changes unless I miss your point.
maybe you do, as you might have costs between the connected network and the connecting batman node.
when you have more then one batman node connecting a network to the mesh, this costs should be relevant.
That might be true, however in batman-adv we are dynamically adding and removing MAC addresses. IMHO, it would not make so much sense to add custom metrics to each mac address. If you need to connect subnets, it might be feasible to use something like BGP and extract batman metrics out of the module.
sure, but as i understand, you have no way of exporting STP and RSTP path costs into batman, which could make sense in a mixed wired/ wireless enviroment. ...
best regards, Simon
Gruss, Alex