dhcpcd-discuss

Hi

On 26/12/16 05:24, shreesha vitthala wrote:
> Hello,
> 
> I have a device running dhcpcd. When I remove the router connection it
> acquires a 169.x.x.x address automatically. But this works mostly when I
> disconnect my PC running Ubuntu 16.04 LTS from the network. I'm using
> this PC to develop and deploy firmware to the device.
> When the PC is connected dhcpcd mostly fails after this line -
> 
>           eth0: probing for an IPv4LL address
> 
> and ends up in segmentation fault.

You also failed to say which dhcpcd version you're running.
Can you upgrade to dhcpcd-6.11.5 please?

Can you post a backtrace please?

> However when I use avahi the eth0:avahi adapter successfully acquires
> 169.x.x.x address even when my PC is connected.
> 
> From the man page I could get below information but it is not sufficent
> for me to pin-point the cause for the failure -
> "
> 
> When using IPv4LL, *dhcpcd* nearly always succeeds and returns an exit code
>      of 0.  In the rare case it fails, it normally means that there is a
>      reverse ARP proxy installed which always defeats IPv4LL probing.
> "
> 
> I found that my PC has RARP installed but it is not running in my
> process list.
> The command I used to find this is "ps -ef|grep rarp"
> 
> Can you please enlighen me on possible causes for this?

Reverse ARP Proxy (or anything similar) only needs to be running on one
device on the same network segment to trigger a false positive for
IPv4LL, does not have to be the same host.

Roy