dhcpcd-discuss

On Saturday 13 Jun 2015 11:43:09 Roy Marples wrote:
> Hi Mick
> 
> On Friday 12 Jun 2015 23:20:40 Mick wrote:
> > I tried the latest from trunk, but it fails to obtain a dhcp address from
> > my router.  :-(
> > 
> > When I pull the cable and push it back in, this is what I get:
> > =============================================================
> > Jun 12 22:56:41  dhcpcd[8128]: timed out
> > Jun 12 22:56:41  ifplugd(enp11s0)[3063]: client: timed out
> > Jun 12 22:56:41  dhcpcd[8128]: dhcpcd exited
> > 
> > Why doesn't it accept address 10.10.10.7 offered from the router?
> 
> It did, but it timed out!
> When I work on dhcpcd, 99% of the time it's in the foreground .... and I
> forgot to add the code to make it background.
> I've quickly added this, but don't have time to test it until Monday ....
> hopefully you can.
> 
> > PS. I've noticed that the router is temperamental - some times it
> > responds to arpings, other times it does not.  Also, with this NIC
> > (BCM5784M) the router does not respond to DHCPREQ to rebind the address
> > when I try to reconnect. Not sure if this is related, but I mention it
> > just in case.
> 
> If you can send me a full tcpdump -s0 of the failing transaction I can
> look. It might be a dhcpcd bug, or an issue with your router.

After some help off list by Roy, the rebinding problem was identified to be 
caused by a rather pedestrian response from my router on DHCPREQUEST packets.  
I added '--reboot 30' and indeed 27-28 seconds later the router eventually 
responds with an IP offer.

This also has the effect of delaying the allocation of an IPv4ALL address, 
using the latest commit.

Thanks again for your help!  :-)

-- 
Regards,
Mick

Attachment: signature.asc
Description: This is a digitally signed message part.