dhcp3-server is launched before NetworkManager and thus doesn't find interfaces
Bug #392826 reported by
Sebastian Kaps
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dhcp3 (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: dhcp3-server
Hi!
I'm running Ubuntu 9.04 (upgraded from 8.10, in case that matters).
I recently switched from using /etc/network/
I'm also running a DHCP server on this machine.
Problem: In /etc/rc2.d the start link for dhcp3-server ist prefixed with S40... and the one for NetworkManager with S50...
Thus dhcp3-server is launched before NetworkManager was able bring all interfaces up, which leaves the DHCP server non-functional since it cannot find the interfaces it was configured to listen on.
Changed in dhcp3 (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
I'm also running into this.
I've bodged around it by putting the attached script in /etc/network/ if-up.d/ dhcp3-server . I don't claim it's the best solution, or that it should be included in the package, but it works for my situation (where I have a single interface "eth0" explicitly listed in /etc/default/ dhcp3-server) , so it might be a useful workaround for others.