dhcpcd-discuss

Re: Can't ping 169 autoip address with multiple NICs

Roy Marples

Mon Dec 12 18:41:28 2011

On Mon, 12 Dec 2011 10:55:08 -0600, Dallas Clement wrote:
After turning on debug with the -d option, these are the debug
messages I'm seeing in the syslog.  Notice that carrier is acquired
only for eth0 as expected.

I'm not seeing dhcpcd configure the 169 addresses, nor see carrier up incorrectly.
Also, the -d flag doesn't look like it's being used.
Try adding the debug command to /etc/dhcpcd.conf

Lastly, you seem to be running a dhcpcd process per interface.
With dhcpcd-5, one process can configure all interfaces which generally works better if multiple interfaces share the same subnet.

As an experiment, try doing this

pkill dhcpcd
sleep 10
dhcpcd -dB

The sleep is to try and ensure no dhcpcd process is still running.
Once you see dhcpcd working in the terminal, you can hit Ctrl-C at any time to halt it. The -B flag basically keeps it in the foreground so you can see what it's doing.

Thanks

Roy

Follow-Ups:
Re: Can't ping 169 autoip address with multiple NICsDallas Clement
References:
Can't ping 169 autoip address with multiple NICsDallas Clement
Re: Can't ping 169 autoip address with multiple NICsRoy Marples
Re: Can't ping 169 autoip address with multiple NICsDallas Clement
Re: Can't ping 169 autoip address with multiple NICsRoy Marples
Re: Can't ping 169 autoip address with multiple NICsDallas Clement
Re: Can't ping 169 autoip address with multiple NICsDallas Clement
Archive administrator: postmaster@marples.name