Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 285505

Summary: net-misc/dhcpcd-4.0.13 fails to acquire lease on bridge interface
Product: Gentoo Linux Reporter: Jason Miller <jason>
Component: Current packagesAssignee: Jeremy Olexa (darkside) (RETIRED) <darkside>
Status: RESOLVED FIXED    
Severity: normal CC: audvare, roy
Priority: High    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: My /etc/conf.d/net

Description Jason Miller 2009-09-18 22:59:41 UTC
Log of messages is below.

dhclient works fine, and so does dhcpcd-4.0.7

Network configuration file is attached

 *   Bringing up br0
 *     dhcp
 *       Running dhcpcd ...
br0: dhcpcd 4.0.13 starting
br0: broadcasting for a lease
br0: offered 192.168.99.250 from 192.168.98.253
br0: acknowledged 192.168.99.250 from 192.168.98.253
br0: checking 192.168.99.250 is available on attached networks
br0: NAK: requested address not available from 192.168.98.253
br0: broadcasting for a lease
br0: offered 192.168.99.250 from 192.168.98.253
br0: acknowledged 192.168.99.250 from 192.168.98.253
br0: checking 192.168.99.250 is available on attached networks
br0: NAK: requested address not available from 192.168.98.253



Reproducible: Always

Steps to Reproduce:
# dhcpcd br0
When the attached network configuration is used.  I've only tried this on one network though, so it may be specific to the dhcp server
Comment 1 Jason Miller 2009-09-18 23:00:38 UTC
Created attachment 204554 [details]
My /etc/conf.d/net
Comment 2 Andrew Udvare 2009-09-22 11:58:52 UTC
Same thing happens for me. Downgraded to 4.0.7, all working fine. It is strange because for me it wanted to get an IP from the correct DHCP server, but then it would say it could not get it from some random server.
Comment 3 Roy Marples 2009-09-24 13:14:49 UTC
This is fixed in dhcpcd-4.0.15
Comment 4 Jeremy Olexa (darkside) (RETIRED) archtester gentoo-dev Security 2009-09-25 13:12:49 UTC
(In reply to comment #3)
> This is fixed in dhcpcd-4.0.15
> 

in tree. thx