Why does metric_to_kernel() overwrite the internal metrics with the fixed, global kernel_metric value before installing the route? Would a "babeld -k copy" option to redistribute Babel metrics into the kernel without modification be an appropriate addition?
Relatedly, has anyone attempted, succeeded, or failed to redistribute Babel into or out of other routing protocols? The path of least resistance would seem to be letting both Babel and another routing daemon act independently, interacting via kernel routes. Exposing the metrics seems like a good idea in general, and entirely necessary if a Babel network exchanges routes with some other network at more than one point. Thanks, --Will Glynn _______________________________________________ Babel-users mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/babel-users
