<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
Hello,<br><br><div>> From: gmazzurco89@gmail.com<br>> On 05/11/12 18:16, Federico Capoano wrote:<br>> > *Routing protocol*<br>> > a device might have more than one routing protocol, think a case in<br>> > which a node functions as a bridge between 2 networks with different<br>> > routing protocols.<br>> > The routing protocol could be installed on a server or an access point,<br>> > or any other machine that has enough resources to run it, that's why I<br>> > advice to have a single table for devices.<br>> > In my opinion routing protocols should be related to the device table<br>> > and it should be possible to assign more than one to a single device.<br>> > <br>> <br>> maybe you some devices like hotspot doesn't have that so i think this<br>> should be out of the core too<br><br>I absolutely don't think that the routing protocol is an attribute of the node but <br>of every single link/neighbour a node has. In the PBerg firmware the default <br>configuration of simultaneous IPv4 an v6 OLSRd routing is to have 2 instances <br>of it running. But to improve the routing in favor of wired links and well built <br>backbone links another metric module is used (etx-ffeth instead of etx-ff). That <br>configuration is standard now in the (very) old FFF and recent backfire firmwares.<br>But because many nodes aren't running this 4and6 configuration yet, there are <br>2 maybe completely different topologies using the same routing daemon on the <br>same node. That should be representable in the database. But there maybe additional <br>routing daemons running on the mentioned gateways (batman(-adv), OSPF, BGP) <br>which may have a completely different set of neighbours or as well an overlapping <br>set. In the latter case it maybe good to know link metric of all routing protocols spoken <br>between 2 nodes.<br><br>Regards<br>Dennis<br></div> </div></body>
</html>