On Fri, 23 Feb 2018 17:33:13 +0100 Matthijs Kooijman
wrote:
> previously, people suggested completely disabling ipv6 as a workaround
> (or at least debugging tool). This, combined with the previous analysis
> made me realize another workaround: Just disable ipv6 autoconf by the
> kernel. I
Hey folks,
previously, people suggested completely disabling ipv6 as a workaround
(or at least debugging tool). This, combined with the previous analysis
made me realize another workaround: Just disable ipv6 autoconf by the
kernel. I dropped these two lines in my sysctl.conf:
Package: network-manager
Version: 1.10.4-1+b1
Followup-For: Bug #755202
Hi folks,
I've also been seeing this bug on my system for quite some while now,
and decided to investigate today. I haven't quite figured it out, but
I'll share my findings here.
>From the previous discussion on this bug,
PS: a very crude workaround for this:
# cat /etc/default/NetworkManager
if [ -z "$(ip -4 addr list dev eth0)" ] && [ -n "$(ip -6 addr list dev
eth0)" ]
then
ip link set down dev eth0
ip addr flush dev eth0
fi
signature.asc
Description: OpenPGP digital signature
Hi folks,
here are some more insights into this mystery:
My "victim" box:
- kvm-guest: jessie, task-xfce-desktop, sysvinit instead of systemd
- running with -net nic,model=rtl8139 -net tap
- connected to br0 of the kvm host which also contains the host's eth0
- the guest's
Actually, since my last message (#161) I
have found that, very, very occasionally, an invalid second eth0
connection is created even in the following situation:
IPv6 enabled in aliases.conf: yes
IPv6 enabled in avahi-daemon.conf: no
[ipv6] method=ignore
[ipv4] method=auto
[ipv4]
Am 19.03.2015 um 18:59 schrieb Fitzcarraldo:
Mar 18 22:17:33 localhost NetworkManager[8346]: info new connection
/etc/NetworkManager/system-connections/eth0
Can you attach this file /etc/NetworkManager/system-connections/eth0?
--
Why is it that all of the instruments seeking intelligent life
Talked to upstream about this problem.
Attached is the IRC log.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
mbiebl dcbw: this bug report is a mess:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755202
mbiebl do you have any
Original Message
*Subject: *Re: [Pkg-utopia-maintainers] Bug#755202: network-manager:
keeps creating and using new connection eth0 that does not work
*From: *Michael Biebl bi...@debian.org
*To: *Fitzcarraldo fitzcarral...@hotmail.com, 755...@bugs.debian.org
*Date: *31/03/15 07:49
I hope you don't mind me commenting again on a Debian bug report, but
this problem occurs across distributions and I think my comments may be
of some relevance to Debian users too.
I'm even more convinced the problem seen by some (not all) of the users
commenting in this thread is due to a bug in
Am 13.03.2015 um 22:18 schrieb Stefano Zacchiroli:
On Fri, Mar 13, 2015 at 10:06:42PM +0100, Michael Biebl wrote:
So, it would be immensly helpful, if someone can provide me with a
detailed description of his network setup (what interfaces are managed
by NetworkManager, what by ifupdown,
I started experiencing this problem in Gentoo Linux (~amd64 installation
using OpenRC) around 5 months ago. Keivan Moradi's fix (Message #79) did
not cure the problem for me, and, in any case, my wired NIC uses a
different driver (atl1c) which appears to be stable in my installation.
I think an
On Fri, Mar 13, 2015 at 10:06:42PM +0100, Michael Biebl wrote:
So, it would be immensly helpful, if someone can provide me with a
detailed description of his network setup (what interfaces are managed
by NetworkManager, what by ifupdown, what's the individual configuration
and available
control: tags -1 moreinfo unreproducible
On Fri, 18 Jul 2014 21:35:52 +0200 Felix C. Stegerman f...@obfusk.net
wrote:
Package: network-manager
Version: 0.9.10.0-1
Severity: normal
Dear Maintainer,
NetworkManager has started creating a new wired connection eth0
after/during boot; this
Hi!
I just came across this bug after reading the latest status report:
https://lists.debian.org/debian-devel-announce/2015/03/msg2.html
I have a laptop that has been running jessie for a few months. I use
NetworkManager to configure the wifi, but use /etc/network/interfaces for
eth0.
I
fredagen den 18 juli 2014 21.35.52 skrev du:
NetworkManager has started creating a new wired connection eth0
after/during boot; this connection has ipv4 (and ipv6) disabled, and
thus provides no connectivity. I can manually select my original
wired connection (standard dhcp) in gnome3 (or
I can assume NM creates virtual 'eth0' profile when it sees that interface is
already brought up and configured.
This profile does not exist as a file in /etc/NetworkManager/system-connections.
I'm using several named connection profiles with associated dispatcher scripts.
If there is a need
severity: important
thanks
Dear network-manager maintainers,
On Fri, Jul 18, 2014 at 09:35:52PM +0200, Felix C. Stegerman wrote:
NetworkManager has started creating a new wired connection eth0
after/during boot; this connection has ipv4 (and ipv6) disabled, and
thus provides no connectivity.
Package: network-manager
Version: 0.9.10.0-1
Severity: normal
Dear Maintainer,
NetworkManager has started creating a new wired connection eth0
after/during boot; this connection has ipv4 (and ipv6) disabled, and
thus provides no connectivity. I can manually select my original
wired connection
19 matches
Mail list logo
