dhcpcd-discuss

Can't ping 169 autoip address with multiple NICs

Dallas Clement

Sat Dec 10 00:57:27 2011

Hi,

I've got two Linux hosts each with four NICs.  If I directly connect a
single cable from one host to the other and use dhcpc to configure the
interfaces, each interface ends up getting a 169 autoip address.  Only
the interface with a cable connected is actually up and running.  This
is what I expect.

If I try to ping the other host over the interface which is up and
running, the ping fails.  I am selecting a specific interface with
ping -I eth0 for example.  I also tried downing the non-cabled
interfaces so that I just have one up and running.  That didn't make
any difference.

Oddly, enough arping -I eth0 169.254.XXX.XXX works just fine.  It's
just ping that fails.

Now if I reconfigure these same interfaces on each box with say a 192
or 172 address instead of a 169 address, ping is successful.  So there
seems to be something peculiar about 169 addresses and multiple NICs.

Is this expected behavior for the scenario described?

I have conducted these tests on Linux 2.6.39.4 kernel with Intel NICs
/ e1000e drivers.  So about as generic as it gets.

Thanks,

Dallas

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