[avahi] running link local address on one interface, dhcp on another

[marty]

I want to learn more about how avahi and link local addresses work (I'm generally an expert on traditional

tcp/ip networking, zeroconf is new to me).

I have a machine running fedora 13 with two ethernet interfaces on the same lan (dell).


One interface (eth0) is dhcp.  I want the other interface to be link-local.  I execute
avahi-autoipd eth1. 
For good measure, I changed /etc/avahi/avahi-daemon.conf to

allow-interfaces=eth1

(but it made no differences.



On remote machines, when I ping the link local interface, I want to see the MAC address of eth1 being 
used.    What I'm seeing is eth0 bound to the link local ip address for eth1.

My target machine looks like:[root at dell init.d]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:C0:9F:12:33:6A  
          inet addr:192.168.0.11  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::2c0:9fff:fe12:336a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2724 errors:0 dropped:0 overruns:0
 frame:0
          TX packets:1207 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:250992 (245.1 KiB)  TX bytes:153082 (149.4 KiB)

eth1      Link encap:Ethernet  HWaddr 00:E0:4C:D0:1A:9D  
          inet6 addr: fe80::2e0:4cff:fed0:1a9d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11116 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
 txqueuelen:1000 
          RX bytes:1845507 (1.7 MiB)  TX bytes:10113 (9.8 KiB)
          Interrupt:27 Base address:0x2000 

eth1:avahi Link encap:Ethernet  HWaddr 00:E0:4C:D0:1A:9D  
          inet addr:169.254.86.144  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          Interrupt:27 Base address:0x2000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128
 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:144 errors:0 dropped:0 overruns:0 frame:0
          TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15090 (14.7 KiB)  TX bytes:15090 (14.7 KiB)

[root at dell init.d]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U    
 1      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

On another machine (asus)
: leisner at asus 11:33:14;arping -I wlan1  169.254.86.144
WARNING: interface is ignored: Operation not permitted
ARPING 169.254.86.144 from 192.168.0.155 wlan1
Unicast reply from 169.254.86.144 [00:C0:9F:12:33:6A]  6.427ms
Unicast reply from 169.254.86.144 [00:C0:9F:12:33:6A]  2.097ms
Unicast reply from 169.254.86.144
 [00:C0:9F:12:33:6A]  1.779ms


I would expect a ping to 169.254.86.144 from a remote machine 
would return a MAC address of  00:E0:4C:D0:1A:9D .  It seems like the kernel "knows"
what's going on.

marty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/avahi/attachments/20111121/7600b433/attachment.html>