dhcpcd-discuss

Hi Renu

Sorry for the late reply.

On 24/08/2018 05:02, Renu Bansal wrote:
> Hi Roy
>
> I am using dhcpcd 6.11.0.

That version is very old.
I no longer support dhcpcd-6.

>   I have run following command
>
> "dhcpcd  -t 130  -y 140 -L -i abc -o 2 -o 3 -o 4 -o 7 -o 42 -o 6 -o 12 
> –o 15 -o 66 -o 120 “
>
> The end device sends the DHCP discover packet at the following intervals:
>
> 4, 8, 16, 32, 64
>
> the above process is not continuous and end device does not send any 
> more DHCP Discover packets after 140sec
>
> following is the output on cli after running the command.
>
> control_open: Connection refused
>
> dhcpcd-6.11.0 starting
>
> –o: interface not found or invalid
>
> 15: interface not found or invalid
>
> eth0: executing `/libexec/dhcpcd-run-hooks' PREINIT
>
> script_runreason: /libexec/dhcpcd-run-hooks: WEXITSTATUS 127
>
> eth0: executing `/libexec/dhcpcd-run-hooks' CARRIER
>
> script_runreason: /libexec/dhcpcd-run-hooks: WEXITSTATUS 127
>
> DUID 00:01:00:01:23:11:df:d4:00:60:b9:99:fa:58
>
> eth0: IAID b9:99:fa:58
>
> eth0: delaying IPv6 router solicitation for 0.4 seconds
>
> eth0: delaying IPv4 for 0.0 seconds
>
> eth0: using hwaddr 00:60:b9:99:fa:58
>
> eth0: soliciting a DHCP lease
>
> eth0: sending DISCOVER (xid 0x43cfa717), next in 4.9 seconds
>
> eth0: soliciting an IPv6 router
>
> eth0: sending Router Solicitation
>
> eth0: Router Advertisement from fe80::1eaa:7ff:feeb:8dc0
>
> eth0: adding route to 2345::/64
>
> eth0: adding default route via fe80::1eaa:7ff:feeb:8dc0
>
> eth0: executing `/libexec/dhcpcd-run-hooks' ROUTERADVERT
>
> script_runreason: /libexec/dhcpcd-run-hooks: WEXITSTATUS 127
>
> eth0: reading lease `/var/db/dhcpcd-eth0.lease6'
>
> eth0: soliciting a DHCPv6 lease
>
> eth0: delaying SOLICIT6 (xid 0x55a5c3), next in 0.6 seconds
>
> eth0: broadcasting SOLICIT6 (xid 0x55a5c3), next in 1.0 seconds
>
> eth0: broadcasting SOLICIT6 (xid 0x55a5c3), next in 2.1 seconds
>
> eth0: broadcasting SOLICIT6 (xid 0x55a5c3), next in 4.1 seconds
>
> eth0: sending DISCOVER (xid 0x43cfa717), next in 7.3 seconds
>
> eth0: broadcasting SOLICIT6 (xid 0x55a5c3), next in 8.3 seconds
>
> eth0: sending DISCOVER (xid 0x43cfa717), next in 15.7 seconds
>
> eth0: broadcasting SOLICIT6 (xid 0x55a5c3), next in 16.6 seconds
>
> eth0: sending DISCOVER (xid 0x43cfa717), next in 31.5 seconds
>
> timed out
>
> forking to background
>
> forked to background, child pid 1195
>
> Earlier version dhcpcd 5.2.12 that I was using retries the dhcp discover 
> after 140sec again in similar fashion i.e 4, 8, 16, 32, 64. This process 
> was continuous until device gets the lease from DHCP Server.o wait

I tested with dhcpcd-7.0.8 and this is the result:
# time ./dhcpcd -d4 -t 130  -y 140 -L -i abc -o 2 -o 3 -o 4 -o 7 -o 42 
-o 6 -o 12 -o 15 -o 66 -o 120
dhcpcd-7.0.8 starting
xennet0: executing `/libexec/dhcpcd-run-hooks' PREINIT
xennet0: executing `/libexec/dhcpcd-run-hooks' CARRIER
DUID 00:01:00:01:20:12:08:0c:fa:73:78:00:00:02
xennet0: IAID 78:00:00:02
xennet0: IA type 25 IAID 00:00:00:01
xennet0: delaying IPv4 for 0.1 seconds
xennet0: reading lease `/var/db/dhcpcd/xennet0.lease'
xennet0: rebinding lease of 10.73.1.62
xennet0: ARP announcing 10.73.1.62 (1 of 2), next in 2.0 seconds
xennet0: sending REQUEST (xid 0x5a150495), next in 3.9 seconds
xennet0: ARP announcing 10.73.1.62 (2 of 2)
xennet0: sending REQUEST (xid 0x5a150495), next in 8.7 seconds
xennet0: sending REQUEST (xid 0x5a150495), next in 15.5 seconds
xennet0: sending REQUEST (xid 0x5a150495), next in 33.0 seconds
xennet0: sending REQUEST (xid 0x5a150495), next in 63.7 seconds
xennet0: sending REQUEST (xid 0x5a150495), next in 63.6 seconds
timed out
forking to background
forked to background, child pid 22158
      130.04 real         0.00 user         0.02 sys
#

So this works fine.
I strongly suggest upgrading.

> One more thing that I want to ask is if I don’t want t

I have no idea what you mean here.
Please re-phrase.

Roy