[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[cetex]

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 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 package in Ubuntu:
  Fix Released
Status in mailman package in Ubuntu:
  Confirmed

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@:~# ip addr show dev lo
  1: lo:  mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@:~# ip addr show dev lo
  1: lo:  mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@:~# ifdown lo

  And up, but this time with --no-loopback:
  root@:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2>/dev/null
  ip addr add dev lo ::1 2>/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  now it seems like something actually happened!

  check:
  root@:~# ip addr show dev lo
  1: lo:  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
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever

  All seems fine, everything is working from here on.

  My expectation is that ifup should configure the interface and set
  state to up, and ifdown should set state to down, even though it's a
  loopback that may or may not be magically autoconfigured somewhere
  else.

  And a question:
  If the case is that ifup shouldn't configure the loopback, what should 
configure it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : 

[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[cetex]

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 bring loopback to state up

Status in ifupdown package in Ubuntu:
  Fix Released
Status in mailman package in Ubuntu:
  Confirmed

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@hostname:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@hostname:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@hostname:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@hostname:~# ifdown lo

  And up, but this time with --no-loopback:
  root@hostname:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2/dev/null
  ip addr add dev lo ::1 2/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  now it seems like something actually happened!

  check:
  root@hostname:~# ip addr show dev lo
  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
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever

  All seems fine, everything is working from here on.

  My expectation is that ifup should configure the interface and set
  state to up, and ifdown should set state to down, even though it's a
  loopback that may or may not be magically autoconfigured somewhere
  else.

  And a question:
  If the case is that ifup shouldn't configure the loopback, what should 
configure it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[cetex]

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” package in Ubuntu:
  Fix Released

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@hostname:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@hostname:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@hostname:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@hostname:~# ifdown lo

  And up, but this time with --no-loopback:
  root@hostname:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2/dev/null
  ip addr add dev lo ::1 2/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  now it seems like something actually happened!

  check:
  root@hostname:~# ip addr show dev lo
  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
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever

  All seems fine, everything is working from here on.

  My expectation is that ifup should configure the interface and set
  state to up, and ifdown should set state to down, even though it's a
  loopback that may or may not be magically autoconfigured somewhere
  else.

  And a question:
  If the case is that ifup shouldn't configure the loopback, what should 
configure it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[cetex]

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
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:9c:02:ab:cb:d8 brd ff:ff:ff:ff:ff:ff
inet6 my:ipv6:address:1/64 scope global temporary dynamic 
   valid_lft 603348sec preferred_lft 84348sec
inet6 my:ipv6:address:2/64 scope global dynamic 
   valid_lft 2591995sec preferred_lft 604795sec
inet6 fe80::29c:2ff:feab:cbd8/64 scope link 
   valid_lft forever preferred_lft forever
3: eth1: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:9c:02:ab:cb:d9 brd ff:ff:ff:ff:ff:ff
inet6 my:ipv6:address:3/64 scope global temporary dynamic 
   valid_lft 603348sec preferred_lft 84348sec
inet6 my:ipv6:address:4/64 scope global dynamic 
   valid_lft 2591995sec preferred_lft 604795sec
inet6 fe80::29c:2ff:feab:cbd9/64 scope link 
   valid_lft forever preferred_lft forever

-- 
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” package in Ubuntu:
  New

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@hostname:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@hostname:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@hostname:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@hostname:~# ifdown lo

  And up, but this time with --no-loopback:
  root@hostname:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2/dev/null
  ip addr add dev lo ::1 2/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing 

[Touch-packages] [Bug 1375821] [NEW] ifupdown doesn't bring loopback to state up

[cetex]

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 eth0 inet ipv4ll

auto eth1
iface eth1 inet6 auto
dhcp 1
#iface eth1 inet ipv4ll

Upon boot Loopback is unconfigured:
root@hostname:~# ip addr show dev lo
1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

Try to bring the interface up:
root@hostname:~# ifup -v lo
ifup: interface lo already configured

Bring it down and up:
root@hostname:~# ifdown -v lo
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts --verbose /etc/network/if-post-down.d
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts --verbose /etc/network/if-post-down.d
Configuring interface lo=lo (inet6)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/avahi-autoipd
run-parts: executing /etc/network/if-down.d/upstart
run-parts --verbose /etc/network/if-post-down.d

root@hostname:~# ifup -v lo
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface lo=lo (inet6)
run-parts --verbose /etc/network/if-pre-up.d
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart

no change:
root@hostname:~# ip addr show dev lo
1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

bring it down again:
root@hostname:~# ifdown lo

And up, but this time with --no-loopback:
root@hostname:~# ifup -v --no-loopback lo
Configuring interface lo=lo (inet)
run-parts --verbose /etc/network/if-pre-up.d
ip link set dev lo up
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart
Configuring interface lo=lo (inet6)
run-parts --verbose /etc/network/if-pre-up.d
ip link set dev lo up 2/dev/null
ip addr add dev lo ::1 2/dev/null
run-parts --verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/avahi-autoipd
run-parts: executing /etc/network/if-up.d/openssh-server
run-parts: executing /etc/network/if-up.d/upstart

now it seems like something actually happened!

check:
root@hostname:~# ip addr show dev lo
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
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever

All seems fine, everything is working from here on.

My expectation is that ifup should configure the interface and set state
to up, and ifdown should set state to down, even though it's a loopback
that may or may not be magically autoconfigured somewhere else.

And a question:
If the case is that ifup shouldn't configure the loopback, what should 
configure it?

** Affects: ifupdown (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: trusty

-- 
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” package in Ubuntu:
  New

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 

[Touch-packages] [Bug 1375821] Re: ifupdown doesn't bring loopback to state up

[cetex]

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 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” package in Ubuntu:
  New

Bug description:
  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 eth0 inet ipv4ll

  auto eth1
  iface eth1 inet6 auto
  dhcp 1
  #iface eth1 inet ipv4ll

  Upon boot Loopback is unconfigured:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Try to bring the interface up:
  root@hostname:~# ifup -v lo
  ifup: interface lo already configured

  Bring it down and up:
  root@hostname:~# ifdown -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-down.d
  run-parts: executing /etc/network/if-down.d/avahi-autoipd
  run-parts: executing /etc/network/if-down.d/upstart
  run-parts --verbose /etc/network/if-post-down.d

  root@hostname:~# ifup -v lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  no change:
  root@hostname:~# ip addr show dev lo
  1: lo: LOOPBACK mtu 65536 qdisc noop state DOWN group default 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  bring it down again:
  root@hostname:~# ifdown lo

  And up, but this time with --no-loopback:
  root@hostname:~# ifup -v --no-loopback lo
  Configuring interface lo=lo (inet)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart
  Configuring interface lo=lo (inet6)
  run-parts --verbose /etc/network/if-pre-up.d
  ip link set dev lo up 2/dev/null
  ip addr add dev lo ::1 2/dev/null
  run-parts --verbose /etc/network/if-up.d
  run-parts: executing /etc/network/if-up.d/avahi-autoipd
  run-parts: executing /etc/network/if-up.d/openssh-server
  run-parts: executing /etc/network/if-up.d/upstart

  now it seems like something actually happened!

  check:
  root@hostname:~# ip addr show dev lo
  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
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever

  All seems fine, everything is working from here on.

  My expectation is that ifup should configure the interface and set
  state to up, and ifdown should set state to down, even though it's a
  loopback that may or may not be magically autoconfigured somewhere
  else.

  And a question:
  If the case is that ifup shouldn't configure the loopback, what should 
configure it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1375821/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :