Help with eth0:avahi

Jordon Bedwell jordon at envygeeks.com
Fri Jul 22 20:04:58 UTC 2011


On 07/22/2011 02:29 PM, don fisher wrote:
> What is eth0:avahi that appears under ifconfig? If eth0 (wireless) is
> active, I never see an eth0:avahi. If I am using eth1, which is a wired
> connection, eth0:avahi appears (see below). Is avahi only interested in
> wireless resources? I do not know what the address 169.254.8.41 refers
> to. I though the inet address were address of my machine on my network.
> 
> I find this all a bit confusing.

According to IANA:
"Autoconfiguration" IP Addresses:

        169.254.0.0 - 169.254.255.255

Addresses in the range 169.254.0.0 to 169.254.255.255 are used
automatically by some PCs and Macs when they are configured to use IP,
do not have a static IP Address assigned, and are unable to obtain an IP
address using DHCP.

This traffic is intended to be confined to the local network, so the
administrator of the local network should look for misconfigured hosts.
Some ISPs inadvertently also permit this traffic, so you may also want
to contact your ISP. This is documented in RFC 5735.

> ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:16:ce:1f:46:cd
>           inet6 addr: fe80::216:ceff:fe1f:46cd/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:2060 errors:0 dropped:0 overruns:0 frame:13405
>           TX packets:1972 errors:1418 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:1960325 (1.9 MB)  TX bytes:448603 (448.6 KB)
>           Interrupt:17 Base address:0xc000

Unless you are on an IPv6 only network this could be why Avahi is
showing up for /only/ eth0, it is/was a second attempt to get an IPv4
address after DHCP failed.  I'm also noticing quite a few problems with
this connection as well.  So I'm also wondering if you might be
experiencing some problems with a past /thought/ to have been fixed
Avahi bug[1]?  Try doing:

apt-get --purge install avahi-autoipd --reinstall
Reinstalling has fixed those problems for other people in the past.

[1]: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/78078


> eth1      Link encap:Ethernet  HWaddr 00:1c:23:a5:c7:e6
>           inet addr:192.168.7.65  Bcast:192.168.7.255  Mask:255.255.255.0
>           inet6 addr: fe80::21c:23ff:fea5:c7e6/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:94529 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:38785 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:59123326 (59.1 MB)  TX bytes:5098817 (5.0 MB)
>           Interrupt:21
> 
> eth0:avahi Link encap:Ethernet  HWaddr 00:16:ce:1f:46:cd
>           inet addr:169.254.8.41  Bcast:169.254.255.255  Mask:255.255.0.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           Interrupt:17 Base address:0xc000
> 
> 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:407 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:407 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:37442 (37.4 KB)  TX bytes:37442 (37.4 KB)




More information about the ubuntu-users mailing list