I'm also able to reliably reproduce this. I always see avahi-autoipd
processes like these pop up when the problem occurs:
$ ps aux | grep avahi-autoipd
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
avahi-a+ 31710 0.0 0.0 2440 816 ?S10:15 0:00
avah
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756140#10
seems to be related too. simply removing eth0 entries from
/etc/network/interfaces for most people affected with various 'networking'
problems seems to make them magically vanish.
either network-manager is not respecting the rules, or so
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 i
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
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.
Best,
Tobias
On Wed, 17 Sep 2014 15:00:50 -0400 Pat
Hi all,
I've been having this problem with two laptops, and continue to have
the problem.
I don't know much about networking, but I managed to "fix" the problem
by editting "/etc/default/avahi-daemon" so that it reads:
AVAHI_DAEMON_DETECT_LOCAL=0
(originally it had a 1 rather than a 0). Then I re
On Mon, Jul 21, 2014 at 05:59:30PM +0200, Frederik Himpe wrote:
> My NetworkManager.conf looks like this:
>
> [main]
> plugins=ifupdown,keyfile
>
> [ifupdown]
> managed=false
FWIW, I've managed=true (everything else is the same), and I'm seeing
the problem nonetheless.
--
Stefano Zacchiroli .
I'm seeing the same problem: every time I boot my system, a network
called "eth0" with disabled IPv4 and IPv6 is selected.
My NetworkManager.conf looks like this:
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
/etc/network/interfaces looks like this:
# This file describes the network
8 matches
Mail list logo
