On Sat, Jan 26, 2008 at 03:27:00PM +0100, Andreas Schwab wrote:
> Jarek Poplawski <[EMAIL PROTECTED]> writes:
>
> > And, after re-reading this bugzilla report, I'm pretty sure the thing
> > should be done with 'ip route change' (but I didn't check if 2.6.24
> > knows about this...).
>
> $ man ip
> [...]
> ip route add - add new route
> ip route change - change route
> ip route replace - change or add new one
> [...]
>
> According to this "replace" should be a superset of "change".
According to this "replace" should be ...ambiguous. I could read this
"my/proper(?) way":
ip route replace - change with new one or add new one
And ...man could be wrong too after all! (...but not me!)
> Also, please check out comment#3, it also fails for replacing a route
> with something different (it's a route to an ipsec tunnel).
It all depends on which routes should be considered different (and it
should be specified somewhere BTW...).
But, I should've added my all reasoning was more about logic, and since
in real life change and replace are often equivalent, and iproute is
famous from using such equivalents in many places, your claim WRT this
man page could be completely right!
There should be only considered, if realization of this doesn't imply
bugs in some other places, like the one which fix caused this
"regression".
Regards,
Jarek P.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
