| 1 |
On Friday 11 September 2009, covici@××××××××××.com wrote: |
| 2 |
|
| 3 |
> However, when I put the -d, it didn't tell me anything except that |
| 4 |
> dhcpcd sent several discover packets and then said timeout, so my |
| 5 |
> original question still remains -- why a timeout with 5.1 with the same |
| 6 |
> dhcpcd.conf and no timeout with 4.0.13. |
| 7 |
|
| 8 |
It may be a bug. The trick is how do you establish who the bug belongs to? |
| 9 |
dhcpcd-5.1 or your router's firmware? |
| 10 |
|
| 11 |
I recall similar incident with my router and an older dhcpcd version (can look |
| 12 |
through the M/L for a URL if you need me to) whereby the MAC address sent by |
| 13 |
dhcpcd was not being picked up by the router. The router was looking for |
| 14 |
that info in the ID field or some such. Having had static IP addresses for |
| 15 |
my LAN machines meant that my PC would not be given the reserved IP address |
| 16 |
and then dhcpcd would eventually time out. My router's firmware was not |
| 17 |
compliant with the respective RFC that dhcpcd was upgraded to. |
| 18 |
|
| 19 |
The fix I came up with was router specific, therefore I do not have a useful |
| 20 |
suggestion for your circumstances I'm afraid - other than: |
| 21 |
|
| 22 |
Try static IP address for your machine (use ifconfig to set this up and route |
| 23 |
to set up the gw). |
| 24 |
|
| 25 |
Try using a different dhcp client to see if the problem persists. |
| 26 |
|
| 27 |
Try updating your router's firmware just in case. |
| 28 |
|
| 29 |
File a bug for dhcpcd-5.1 with your findings. |
| 30 |
|
| 31 |
PS. Other than testing is there a reason why you don't use a stable dhcpcd |
| 32 |
version? |
| 33 |
-- |
| 34 |
Regards, |
| 35 |
Mick |
Archives