> Op 20 feb. 2015, om 09:54 heeft Henning Rogge <[email protected]> het volgende > geschreven: > > On Fri, Feb 20, 2015 at 9:51 AM, Teco Boot <[email protected]> wrote: >>> At the moment I just get the ethernet port link speed... that is not >>> really good for switched ports, but its better than nothing. >>> http://olsr.org/git/?p=oonf.git;a=blob;f=src-plugins/generic/eth_listener/eth_listener.c;h=1646a60722d60c54d7ab6b5df2e67fba7d52de22;hb=master >>> >>> If you have hardware with a built-in switch that can report the >>> link-speed, it would be easy to add code that integrates this (and >>> some traffic statistics). >> >> Your SW depends on ethtool, right? Not a problem, this is implementation >> detail. Link speed probes could be added for verification the ethtool >> provided info. > > No, it does directly call into the operation system. Calling a > different executable and parsing the output is a good source for > subtle bugs.
Great. > >> And yes, I didn't mean we cannot use the 80% solution. What I want to say is >> that the Homenet Routing Protocol shall be able to use all the link metrics >> it can get. >> >> I am still worried about loops caused by dynamic link metrics used by a link >> state routing protocol. For me, this is the major difference between ISIS >> and Babel. Thats because I don't code the protocol. If I was, I would be >> worried about the non-IP transport in ISIS. > > It is a matter of metric stability... so you need a good hysteresis > and post-processing to make it work. I wonder. If the change hits the hysteresis threshold, two actions will happen. SPF calculation is triggered and routes may change. This would take place in sub-ms. The other action is sending link state to neighbors or flood over the whole network. That takes time, especially when there is no triggered update, there are some packets queued, there is a shared medium with timer based media access etc. Meanwhile, the topology is not guaranteed to be loop-free. Little you can do on the node itself. OK, we have the enterprise/ISP loop avoidance mechanisms, but to reuse this in homenet? Deploy this year? I highly appreciate your work on olsrd/olsrd2, of course !! Teco _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
