On Tue, 18 Aug 2015, Juliusz Chroboczek wrote:
(If you test this with Babel, you need to set "reflect-kernel-metric true"
in babeld's config file; Pierre tells me that this is done automatically
by hnetd. I'll make some refinements to the reflect-kernel-metric code,
and make it the default in the next release of babeld.)
What does that do?
From: http://www.pps.univ-paris-diderot.fr/~jch/software/babel/babeld.html
reflect-kernel-metric {true|false}
Reflect route metrics as kernel priorities. The priority effectively used
is kernel-priority + metric.
http://linux-ip.net/html/routing-selection.html
"The kernel begins iterating by priority through the routing policy
database. For each matching entry in the RPDB, the kernel will try to find
a matching route to the destination IP address in the specified routing
table using the aforementioned longest prefix match selection algorithm.
When a matching destination is found, the kernel will select the matching
route, and forward the packet. If no matching entry is found in the
specified routing table, the kernel will pass to the next rule in the
RPDB, until it finds a match or falls through the end of the RPDB and all
consulted routing tables."
So it takes whatever metric it came up with and sets the metric as kernel
priority? So if there is a shorter prefix that has a lower metric, this
will be chosen over a longer prefix with higher metric?
--
Mikael Abrahamsson email: [email protected]
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
