On Friday 11 September 2009, cov...@ccs.covici.com wrote: > However, when I put the -d, it didn't tell me anything except that > dhcpcd sent several discover packets and then said timeout, so my > original question still remains -- why a timeout with 5.1 with the same > dhcpcd.conf and no timeout with 4.0.13.
It may be a bug. The trick is how do you establish who the bug belongs to? dhcpcd-5.1 or your router's firmware? I recall similar incident with my router and an older dhcpcd version (can look through the M/L for a URL if you need me to) whereby the MAC address sent by dhcpcd was not being picked up by the router. The router was looking for that info in the ID field or some such. Having had static IP addresses for my LAN machines meant that my PC would not be given the reserved IP address and then dhcpcd would eventually time out. My router's firmware was not compliant with the respective RFC that dhcpcd was upgraded to. The fix I came up with was router specific, therefore I do not have a useful suggestion for your circumstances I'm afraid - other than: Try static IP address for your machine (use ifconfig to set this up and route to set up the gw). Try using a different dhcp client to see if the problem persists. Try updating your router's firmware just in case. File a bug for dhcpcd-5.1 with your findings. PS. Other than testing is there a reason why you don't use a stable dhcpcd version? -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
