dhcpcd-discuss

Logs as below. And I think we did not get this behavior when we first
request for a link local address.

I checked the code, did not find out how this could happen. And is this
something deliberately done? a feature or a bug?

thanks, Xia Weizhong

version 5.2.10 starting
wlan0: using ClientID 01:00:e4:cc:13:d0:14
wlan0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason PREINIT
host does not support a monotonic clock - timing can skew
wlan0: reading lease `/data/misc/dhcp/dhcpcd-wlan0.lease'
wlan0: checking for 169.254.27.123
wlan0: sending ARP probe (1 of 3), next in 1.25 seconds
wlan0: sending ARP probe (2 of 3), next in 1.87 seconds
wlan0: sending ARP probe (3 of 3), next in 2.00 seconds
wlan0: using IPv4LL address 169.254.27.123
wlan0: adding IP address 169.254.27.123/16
wlan0: adding route to 169.254.0.0/16
wlan0: writing lease `/data/misc/dhcp/dhcpcd-wlan0.lease'
wlan0: executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason IPV4LL
wlan0: sending ARP announce (1 of 2), next in 2.00 seconds
wlan0: sending ARP announce (2 of 2)
wlan0: broadcasting for a lease
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 3.71 seconds
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 8.50 seconds
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 16.46 seconds
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 32.87 seconds
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 63.53 seconds
wlan0: sending DISCOVER (xid 0xf3f9e70a), next in 64.15 seconds