[Expired for upstart (Ubuntu) because there has been no activity for 60
days.]
** Changed in: upstart (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716429
Sure, I wasn't suggesting that /etc/network/interfaces was buggy, only
that there was something special about the contents. But you're right,
this is pretty simple - and has been tested to work reliably in other
circumstances.
You do have udev on this system, right, you haven't forcibly removed i
PS: The previous entry was only an example - please don't put too much
energy into the details of the routes or such.
Even absolute simple configurations on other machines (without the
routes and using eth0 instead) are behaving like this.
Perhaps the hardware details are more interesting here (t
/etc/networking/interfaces isn't existing; guess you meant
/etc/network/interfaces :
v == START == v
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet l
Please show the contents of your /etc/networking/interfaces file.
Please also show the output of 'status mountall'.
/etc/init.d/networking is not used for bringing up network interfaces in
Ubuntu 9.10 and later; instead network interfaces are normally brought
up via /etc/init/network-interface.co
** Package changed: ubuntu => upstart (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716429
Title:
Networking not automatically available after reboot
--
ubuntu-bugs mailing list
ubuntu-bu
