On za, 2014-10-11 at 09:41 +0200, Stefano Zacchiroli wrote: > On Sat, Oct 11, 2014 at 12:48:25AM +0200, Tobias Hansen wrote: > > Control: severity -1 serious > > > > I'm also having this problem and setting AVAHI_DAEMON_DETECT_LOCAL=0 > > didn't help in my case. I also have this eth0:avahi entry in ifconfig. > > Raising severity since we really don't want to have this bug in a release. > > Same here: it is indeed avahi related (I invariably get a 169.254.7.253 > address) but AVAHI_DAEMON_DETECT_LOCAL=0 doesn't help.
On my system it is not avahi related: I do not have this eth0:avahi address. However, I do get an IPv6 address via SLAAC on the affected system. My guess is that the fact that the fact that there is already an IP assigned to eth0 at the networkmanager start up, provokes this bug. After system start up, I then have an IPv6 address but not an IPv4 address and I have to switch to "Auto Ethernet" network in networkmanager to get an IPv4 address via DHCP in order to have a fully working network configuration. -- Frederik Himpe <fhi...@telenet.be> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
