Daniel Ng
2008-03-17 06:33:15 UTC
Hi,
Using Quagga-0.99.9 with Linux Kernel 2.6.14:
I've noticed that when I specify a metric (of 66) for static routes configured
in zebrad, the metric is reported as '0' if I use the Linux 'route' command or
it's not reported at all if I use the 'ip route' Linux command:
quagga# sh ip ro
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
...
S>* 98.98.98.98/32 [66/0] via 10.100.100.1, ppp2
...
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
...
98.98.98.98 10.100.100.1 255.255.255.255 UGH 0 0 0 ppp2
...
# ip route
...
98.98.98.98 via 10.100.100.1 dev ppp2
...
Does this mean the static route metric was not properly communicated to the
Kernel from Quagga? Changing the route metric doesn't make a difference.
Using Quagga-0.99.9 with Linux Kernel 2.6.14:
I've noticed that when I specify a metric (of 66) for static routes configured
in zebrad, the metric is reported as '0' if I use the Linux 'route' command or
it's not reported at all if I use the 'ip route' Linux command:
quagga# sh ip ro
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
I - ISIS, B - BGP, > - selected route, * - FIB route
...
S>* 98.98.98.98/32 [66/0] via 10.100.100.1, ppp2
...
# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
...
98.98.98.98 10.100.100.1 255.255.255.255 UGH 0 0 0 ppp2
...
# ip route
...
98.98.98.98 via 10.100.100.1 dev ppp2
...
Does this mean the static route metric was not properly communicated to the
Kernel from Quagga? Changing the route metric doesn't make a difference.