*** This bug is a duplicate of bug 82335 ***
https://bugs.launchpad.net/bugs/82335
** This bug has been marked a duplicate of bug 82335
network-manager should not set offline mode when it manages no device
--
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.la
Tracked the problem down to NetworkManager. Implementing the steps
necessary to turn off NetworkManager as referenced in bug # 82335
alleviates the problem.
As stated in bug # 82335, NetworkManager really needs not to cause this
conflict on a purely statically addressed machine.
--
adding non-d
Changed package to reflect actual source of the problem.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: ifupdown => network-manager
--
adding non-default route in /etc/network/interfaces doesn't work
https://bugs.launchpad.net/bugs/97058
You received this bug notification because you
After booting, the "up route ..." line is not run, as evidenced by
"netstat -r" not showing the route specified. However, running
"/etc/init.d/networking stop" followed by "/etc/init.d/networking start"
after boot runs the "up route ..." line. Race condition of some sort,
perhaps, at boot time?
