[Bug 702802] Re: event "net-device-up" is triggered too early

[Tore Anderson]

Indeed. This happens also with IPv6 interfaces, independently of any
specific delay caused by the hardware, as the ifup scripts doesn't
ensure that IPv6 Duplicate Address Detection has completed, nor that
Stateless Address Auto-Configuration has.

In the following case, /etc/network/interfaces contains the following:

auto eth0
iface eth0 inet6 auto

..and I've also created /etc/init/network-test.conf containing the
following:

start on net-device-up IFACE=eth0 ADDRFAM=inet6
exec /sbin/ip a l dev eth0 | logger -t "network-test"

Mar 24 13:53:48 ucstest kernel: [   21.922952] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Mar 24 13:53:48 ucstest network-test: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
Mar 24 13:53:48 ucstest network-test:     link/ether 00:25:b5:00:00:ce brd ff:ff:ff:ff:ff:ff
Mar 24 13:53:48 ucstest network-test:     inet6 fe80::225:b5ff:fe00:ce/64 scope link tentative 
Mar 24 13:53:48 ucstest network-test:        valid_lft forever preferred_lft forever
Mar 24 13:53:48 ucstest ntpdate[1045]: name server cannot be used: Temporary failure in name resolution (-3)

As you can see, this also broke /etc/network/if-up.d/ntpdate, which
could not resolve the NTP server host-name (even if it could, it would
have no chance of actually contacting any NTP server in any case).

This makes it pretty hard (impossible?) to write an upstart script that
will reliably not run until the network is ready, DNS lookups are
possible, and so forth.

Tore

-- 
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/702802

Title:
  event "net-device-up" is triggered too early

Status in “ifupdown” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: ifupdown

  Hello,

  on booting, the event "net-device-up" is triggered too early. The
  event is "sent" to other jobs immediately after the ifup command has
  been executed, but neither ifup nor the calling script /etc/network
  /if-up.d/upstart perform a test if the network connection is really
  working. The result of this behaviour is that a job needing network
  functionality, e.g. mounting NFS filesystems, is possibly started
  before other network machines are reachable and makes the computer
  hang. This happens when the network interface needs some time to
  negotiate the ethernet parameters with the network switch.

  Regards
    Christoph

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: ifupdown 0.6.8ubuntu29.2
  ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
  Uname: Linux 2.6.32-27-generic x86_64
  Architecture: amd64
  Date: Fri Jan 14 10:27:30 2011
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: ifupdown

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