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

Tore Anderson tore at fud.no
Mon Mar 24 17:59:01 UTC 2014


Hi, I forgot to mention that the problems I reported in comment #5 was
reproduced on Ubuntu 12.04.4. I'm glad to hear that it has been since
fixed, but since 12.04.4 is supposed to be «Long Term Support», perhaps
it would be an idea to backport the fix for IPv6 DAD? Thanks for
considering. :-)

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:
  Fix Released

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



More information about the foundations-bugs mailing list