[Bug 890189] Re: `restart networking` does not deconfigure an interface
Steve Langasek
steve.langasek at canonical.com
Fri Jan 6 19:04:21 UTC 2012
> And, last but not least. It's Ubuntu's decision to implement
> upstart, please do that the right way without introducing
> regressions.
A change in behavior is not a regression. The supported way to bring
the interfaces down and up again is to use 'ifup' and 'ifdown', not to
use the init script or upstart job.
This bug is still marked incomplete because you've described a problem
with trying to add duplicate routes that I can't account for.
restarting the network, by any of the above means, should not result in
such an error.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/890189
Title:
`restart networking` does not deconfigure an interface
Status in “ifupdown” package in Ubuntu:
Incomplete
Bug description:
The old /etc/init.d/networking script deconfigured all the interfaces
defined in /etc/network/interfaces. By running `/etc/init.d/networking
restart`, one could make sure that all the old addresses and routes
were removed. The replacementscript for upstart doesn't do anything to
deconfigure an interface. So if you restart networking, a second
default route can be added. Which isn't what you'd expect.
Furthermore, the exitcode always seems to be '0', eventhough ifup
presents errors.
root at vps9124:/etc/init# /etc/init.d/networking restart
* Reconfiguring network interfaces... SIOCADDRT: File exists
Failed to bring up eth0.
[ OK ]
root at vps9124:/etc/init# echo $?
0
root at vps9124:/etc/init# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.04.3 LTS
Release: 10.04
Codename: lucid
IMHO, this is unexpected and unwanted behaviour..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/890189/+subscriptions
More information about the foundations-bugs
mailing list