dhcpcd-discuss

Hi Roy

Thanks for the reply.  After reading through the ticket you indicated mine was a duplicate, I compiled trunk.  Running trunk the prior issue was resolved, however I am now getting an intermittent SegFault issue.

It looks like sometimes the offer does not return soon enough, then ": probing for an IPv4LL address" step occurs, which results in SegFault.  If needed I can provide an strace file of the SegFault.

Thanks again

diana

[root@s981241 ~]# ifconfig eth1 up;sleep 10;strace -o dhcpcd.trace  dhcpcd --nohook resolv.conf --debug --nobackground --ipv4only eth1
control_open: Connection refused
dhcpcd-6.11.0 starting
eth1: executing `/libexec/dhcpcd-run-hooks' PREINIT
eth1: executing `/libexec/dhcpcd-run-hooks' CARRIER
DUID 00:01:00:01:1e:d7:4f:68:0c:c4:7a:6b:07:f3
eth1: IAID 7a:6b:07:f3
eth1: delaying IPv4 for 0.8 seconds
eth1: soliciting a DHCP lease
eth1: sending DISCOVER (xid 0xf07726bb), next in 5.0 seconds
eth1: sending DISCOVER (xid 0xf07726bb), next in 7.5 seconds
eth1: probing for an IPv4LL address
eth1: probing for 169.254.82.95
eth1: ARP probing 169.254.82.95 (1 of 3), next in 1.7 seconds
Segmentation fault (core dumped)



________________________________________
From: Roy Marples <roy@xxxxxxxxxxxx>
Sent: Monday, June 6, 2016 3:46 AM
To: dhcpcd-discuss@xxxxxxxxxxxx
Subject: [EXTERNAL] Re: [dhcpcd-discuss] ARP probe not checking for valid IP in reply

Hi Diana

On 02/06/2016 20:27, Eichert, Diana wrote:
> I am running 6.11.0 on RHEL 6.8.
>
> I see the following when the system makes a DHCP request.  The DHCP
> server provides a valid IP address, but when the system does an ARP
> request for the assigned IP address a broken system on the network
> responds that it is "0.0.0.0".
>
> SNIP eth1: ARP probing 10.3.8.204 (1 of 3), next in 1.6 seconds eth1:
> hardware address 00:16:5d:4f:53:ac claims 0.0.0.0 SNIP
>
> My last C coding was done ~ 25 years ago, but it looks like the code
> does not check whether the ARP reply is valid, but ARP reply !NULL.
> I did see where ARP replies from itself are ignored.
>
> I submitted a ticket too.

http://roy.marples.name/projects/dhcpcd/info/05a4883e1e
Should be fixed for the next release.

Roy