Hi!
I've tested your patch, and it's still using ifconfig in network-interface.conf
it should use ip instead.
what's in network-interface.conf:
ifconfig lo 127.0.0.1 up || true
what should be in network-interface.conf:
ip link set dev lo up || true
--
You received this bug
yeah. but net-tools is deprecated, so this really should be fixed in all
releases. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't
Will this be updated in trusty as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1375821
Title:
ifupdown doesn't bring loopback to state up
Status in “ifupdown”
I forgot to include, other interfaces (eth*) are configured as expected
upon boot:
root@hostname:~# ip addr show
1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue state UNKNOWN group
default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
Public bug reported:
Upon booting a machine with the following setup on a relatively slimmed
down netboot machine the loopback interface isn't brought up properly:
cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface lo inet6 loopback
auto eth0
iface eth0 inet6 auto
dhcp 1
#iface
I found an upstream bugreport detailing the actual issue in ifupdown source on
debian's bugtracker here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757291
** Bug watch added: Debian Bug tracker #757291
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757291
--
You received this bug
6 matches
Mail list logo