Ubuntu

Network not enabled properly by NetworkManager which configures eth1:avah

Bug #105872 reported by Marc Tardif
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

After installing Ubuntu 20070411 from the alternate CD on both amd64 and i386, some machines seem to cause NetworkManager to assign an address to the eth1:avah interface rather than eth0. For example, this is the output of the ifconfig command for the eth1:avah interface on a Sun Ultra 20 M2 workstation:

eth1:avah Link encap:Ethernet HWaddr 00:14:4F:3A:65:F5
          inet addr:169.254.7.190 Bcast:169.254.255.255 Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Interrupt:22 Base address:0x8000

Then, running dhclient assigns an address to eth0 properly from the DHCP server and the eth1:avah interface disappears temporarily from the output of the ifconfig command. A minute later, the eth1:avah interface appears again but eth0 is still properly assigned.

Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
Marc Tardif (cr3) wrote :
Revision history for this message
8200 (8200) wrote :

I have got the same problem here with Ubuntu 7.04 and some i386 Notebook.

Ismael (ismaelgfk)
Changed in network-manager:
status: Unconfirmed → Confirmed
Revision history for this message
bb (klappauf) wrote :

these reports all seem to be old but I have the same problem now after upgrading to ubuntu7, I still don't see any solutions posted.

b

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

ooops

Changed in network-manager:
assignee: nobody → ubuntu-kernel-team
Revision history for this message
ekso (ekso) wrote :

I've got that some weird problem. Maybe that eth1:avah is related to this?

http://avahi.org/

If you search for avah in synaptic you find: Avahi IPv4LL network address configuration daemon

But I'm a less-than-a-month-linux-user...

Revision history for this message
Brian Murray (brian-murray) wrote :

I'm not clear on what exactly the bug here is. If it is that devices are receiving a virtual interface from avahi for eth1 that is not a bug but by design. Avahi allows a network to be created for devices without having a dhcp server in place. You can learn more about avahi at http://en.wikipedia.org/wiki/Avahi_%28software%29 .

Revision history for this message
pooryorick (net-launchpad-pooryorick) wrote :

I couldn't get an IP4 address on my wireless interface, but worked around the problem by doing this:

sudo apt-get uninstall avahi-daemon
find /etc/network -iname 'avahi*' -exec rm {} \;

removing avahi files from /etc/network was the key for me.

Revision history for this message
Polly (pollyp) wrote :

I had a problem with Ubuntu 7.04, where I couldn't get an IPv4 address via DHCP over my wireless interface. However, DHCP worked fine over my wired interface, and if I configured my wireless interface to use a static address that worked too. Because roaming mode assumes that it's a DHCP client, that didn't work either. Iwconfig reported sensible values in both the DHCP and static cases. The eth1:avah interface appeared transiently, as reported above.

Per the last poster's suggestion, I removed /etc/network/*/avahi* and that fixed the problem.

This was on a i386 machine, using the alternate CD install. I'm using an Orinoco 802.11B "silver" card.

Revision history for this message
Brian Murray (brian-murray) wrote :

I'm closing this bug report since there wasn't a response from the original reporter regarding the information needed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.