On Wed, May 08, 2013 at 11:55:10PM +0200, Michael Biebl wrote:
Bad timing. I was probably too eager with my upload a few minutes ago
closing this bug. This still looks fishy.
Should this bug be reopened, then?
--
Antti-Juhani Kaijanaho, Jyväskylä, Finland
Am 08.05.2013 10:41, schrieb Antti-Juhani Kaijanaho:
On Tue, May 07, 2013 at 11:45:47PM +0200, Michael Biebl wrote:
Could you please try the packages from
deb http://people.debian.org/~biebl/network-manager ./
They should fix the ifupdown plugin to correctly track mac address
changes.
On Wed, May 08, 2013 at 08:11:38PM +0200, Michael Biebl wrote:
Am 08.05.2013 10:41, schrieb Antti-Juhani Kaijanaho:
Of course, now nm claims I'm not connected, but I think that's a feature,
not a
bug, with this arrangement.
Actually, no. I've added Debian specific patches to track the
Am 08.05.2013 23:50, schrieb Antti-Juhani Kaijanaho:
On Wed, May 08, 2013 at 08:11:38PM +0200, Michael Biebl wrote:
Am 08.05.2013 10:41, schrieb Antti-Juhani Kaijanaho:
Of course, now nm claims I'm not connected, but I think that's a feature,
not a
bug, with this arrangement.
Actually, no.
On Wed, May 08, 2013 at 11:55:10PM +0200, Michael Biebl wrote:
Bad timing. I was probably too eager with my upload a few minutes ago
closing this bug. This still looks fishy.
I guess I'll have to setup a test environment to reproduce this this
properly.
Curious thing: if I have a clean
On Tue, May 07, 2013 at 11:45:47PM +0200, Michael Biebl wrote:
Could you please try the packages from
deb http://people.debian.org/~biebl/network-manager ./
They should fix the ifupdown plugin to correctly track mac address
changes. Please report back with your results.
I had to delete
Package: network-manager
Version: 0.9.8.0-4
Severity: normal
I have this new laptop of mine configured so that ifupdown manages eth0 (due to
what looks to be #665439).
8-- /etc/network/interfaces
ajk@teralehti:~$ cat /etc/network/interfaces
# This file describes the network
Am 07.05.2013 10:53, schrieb Antti-Juhani Kaijanaho:
Package: network-manager
Version: 0.9.8.0-4
Severity: normal
I have this new laptop of mine configured so that ifupdown manages eth0 (due
to
what looks to be #665439).
8-- /etc/network/interfaces
ajk@teralehti:~$ cat
On Tue, May 07, 2013 at 04:08:23PM +0200, Michael Biebl wrote:
What does
sudo grep 'type=802-3-ethernet' /etc/NetworkManager/system-connections/*
say?
ajk@teralehti:~$ sudo grep 'type=802-3-ethernet'
/etc/NetworkManager/system-connections/*
found 707070 0.9.4.0-10
thanks
Am 07.05.2013 16:34, schrieb Antti-Juhani Kaijanaho:
On Tue, May 07, 2013 at 04:08:23PM +0200, Michael Biebl wrote:
What does
sudo grep 'type=802-3-ethernet' /etc/NetworkManager/system-connections/*
say?
ajk@teralehti:~$ sudo grep 'type=802-3-ethernet'
On Tue, May 07, 2013 at 04:38:11PM +0200, Michael Biebl wrote:
Am 07.05.2013 16:34, schrieb Antti-Juhani Kaijanaho:
ajk@teralehti:~$ sudo grep 'type=802-3-ethernet'
/etc/NetworkManager/system-connections/*
/etc/NetworkManager/system-connections/Automaattinen,
kiinteä:type=802-3-ethernet
Am 2013-05-07 10:53, schrieb Antti-Juhani Kaijanaho:
Package: network-manager
Version: 0.9.8.0-4
Severity: normal
I have this new laptop of mine configured so that ifupdown manages
eth0 (due to
what looks to be #665439).
8-- /etc/network/interfaces
ajk@teralehti:~$ cat
Hi again,
Am 07.05.2013 22:39, schrieb Michael Biebl:
So, the issue here seems to be, that you are changing the mac address of
the interface, and the ifupdown plugin doesn't listen to mac address
changes and updates the unmanaged specs for that.
Could you please try the packages from
deb
13 matches
Mail list logo
