> Op 20 feb. 2015, om 09:22 heeft Henning Rogge <hro...@gmail.com> het volgende > geschreven: > > On Fri, Feb 20, 2015 at 9:19 AM, Teco Boot <t...@inf-net.nl> wrote: >>> There is also the "linklayer database" approach I selected for my >>> olsrd2 implementation. Instead of hardcoding linklayer specific code >>> into the metric, I split the codebase into "link layer gathering" code >>> (which is often OS and linklayer specific), generic routing metric >>> code... and a generic API in between that stores the values. >>> >>> This makes it quite easy to adapt the codebase to new linklayer types. >>> >> >> So you have the placeholder for an automatic ethernet link speed detection. >> Great! >> >> We cannot trust ethernet port L2 feedback. Ports can be connected to >> switches with multi-rate ports. Could be powerline, wired_over_wireless >> bridges or other stuff that hides a slow link. In homes, there is no place >> for protocols that cannot detect and handle such cases. > > 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. 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. Teco _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
