> > 1. The interface metric is ignored.
>
> It is worth to note, that it never was used. 8)
> Certainly, it is not used in 2.2 too.
Now I have an "ip" that knows about metric but... :-)
It seems metric is used as part of the key used to identify the
route. Is that right?
e.g.:
# ip route
...
default dev eth1
# ip route replace default dev eth1 metric 1
# ip route
...
default dev eth1
default dev eth1 metric 1
I was sort of hoping it would just change the metric since the
destination, device, gateway etc. all matched :-(.
Mike
--
A train stops at a train station, a bus stops at a bus station.
On my desk I have a work station...
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: mailto:mike@roan.co.uk |
| Roan Technology Ltd. | |
| 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 |
| RG40 1XG, ENGLAND | Fax: +44 118 989 1195 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/