Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 190883 - NetworkManager malfunctions with dhcp 3.1.0
Summary: NetworkManager malfunctions with dhcp 3.1.0
Status: RESOLVED DUPLICATE of bug 185888
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-31 14:14 UTC by Bas Westerbaan
Modified: 2007-08-31 14:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bas Westerbaan 2007-08-31 14:14:21 UTC 
When dhcp was updated from 3.0.6 to 3.1.0 dhcdbd malfunctions causing NetworkManager to revert to autoip which means no working IP address.  /var/log/messages excerpt:

 Aug 31 15:54:31 t60bw NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
 Aug 31 15:54:32 t60bw NetworkManager: <info>  Activation (eth1) Beginning DHCP transaction.
 Aug 31 15:54:32 t60bw NetworkManager: <info>  Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
 Aug 31 15:54:32 t60bw NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth1
 Aug 31 15:54:32 t60bw dhcdbd: Unrequested down ?:3
 Aug 31 15:54:32 t60bw NetworkManager: <info>  DHCP daemon state is now 14 (normal exit) for interface eth1

When reverted back to 3.0.6 everything works fine again.

Reproducible: Always

Steps to Reproduce:




dhcdbd-2.8-r1 was used
Comment 1 Roderick B. Greening 2007-08-31 14:25:09 UTC 
This was a known issue with NetworkManager. The NetworkManager ebuild should be updated with a dep on dhcp < 3.1.0 to ensure newer is not used.

Preferably, a patch to NetworkManager to make dhcp 3.1.0 play nice with it...
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2007-08-31 14:29:20 UTC 

*** This bug has been marked as a duplicate of bug 185888 ***