Silently? Didn't you get a big fat error message? Silent breakage was what the original commit I pointed you to fixed.
Sure, but I got it when it was already to late - after the upgrade of iproute and the following reboot for a new kernel image. Then I was wondering why my server did not come back on the network and had to run down to our server room... :-)
To use "ip route" in this way was possible for as long as I can think about it. With Debian at least till etch - if this behavior will now be removed by the new upstream version in lenny, then I would say it should be noted somewhere (readme, warning during upgrade, manpage, wherever).
Because now that I know what will happen, I can schedule checking /etc/network/interfaces on our 200 etch servers before upgrading them to lenny :-)
Regards, Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
