udev brings network connections up in the background

Bug #77325 reported by Liam Bedford
8
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ifupdown

udev brings network connections up when it sees the device appear,
using /etc/udev/rules.d/85-ifupdown.rules

There is no way to stop it bringing them up, and it brings them up in
the background. This means that if you're using autofs with ldap
maps, and using dhcp on a network with Spanning Tree Protocols,
so there's a 30 second delay for the port to come up, and a delay for
dhcp to kick in, most of the init scripts will start before the network
comes up. In this case, autofs starts before the network is up, so it
can't read the ldap entries for automount, and you get no automounter.

The workarounds I'm using at the moment include nuking /etc/udev/rules.d/85-ifupdown.rules,
or adding a script to restart autofs in /etc/network/if-up.d/.

A better change might be to change /etc/udev/rules.d/85-ifupdown.rules
from
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pid
file /var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}
"
to
ACTION=="add", RUN+="/sbin/start-stop-daemon --start --background --pid
file /var/run/network/bogus --startas /sbin/ifup -- --allow udev $env{INTERFACE}
"
but I don't know how classes work in /etc/network/interfaces

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

The correct way to fix this will be to use upstart jobs for the daemons

Revision history for this message
Gaetan Nadon (memsize) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.
BugSquad

Changed in ifupdown:
status: New → Incomplete
Revision history for this message
Gaetan Nadon (memsize) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
BugSquad

Changed in ifupdown:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.