dhcpcd-discuss

On Thu, 2008-11-27 at 09:23 +0100, Jean Wolter wrote:
> Both changes work fine:
> 
> Wed Nov 26 19:52:20 2008: eth2: sending ARP probe (1 of 3), next in 1.02 seconds
> Wed Nov 26 19:52:20 2008: eth2: ignoring offer of 192.168.1.33 from 192.168.1.1
> Wed Nov 26 19:52:21 2008: eth2: ignoring offer of 85.5.83.104 from 138.187.24.10
> Wed Nov 26 19:52:21 2008: eth2: sending ARP probe (2 of 3), next in 1.18 seconds
> Wed Nov 26 19:52:23 2008: eth2: sending ARP probe (3 of 3), next in 2.00 seconds
> Wed Nov 26 19:52:25 2008: eth2: sending DHCP_REQUEST with xid 0x5a7e98f9, next in 4.69 seconds
> 
> I booted the same setup on top of a 2.4 linux kernel, which does
> not provide a monotonic clock - dhcpcd detected it correctly,
> displayed the warning and used gettimeofday.

Excellent stuff.
I've commited the clock warning patch to trunk and dhcpcd-4.0 branch.
The timer patch is only relevant for dhcpcd-4.0 as we have a totally new
state engine for 5.0 so we can handle multiple interfaces.

As your interface link seems to flap (which causes this bug I think), it
might be an idea to try out a snapshot to see if it happens with that.
You can download it from here.
ftp://roy.marples.name/pub/dhcpcd/dhcpcd-4.99.6.tar.bz2

It does not have the clock warning patch applied to it, but otherwise
should work fine.

Thanks

Roy

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