desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #157191
[Bug 1535635] [NEW] NetworkManager does not really ignore devices, disturbing udev
Public bug reported:
Hi,
I'm just trying to configure an ubuntu machine to work as a network
controller (dhcp, dns,...) for several virtual and physical machines,
using a linux bridge as a virtual network, and trying to automatically
add USB-Ethernet-Devices to the bridge through udev.
Unfortunately my udev rules fail since Network Manager does rename new
Ethernet devices *before* udev runs, e.g.
eth0 to enx0000e80006d8
for my USB ethernet device. Thus, many regular udev rules fail since
they use the device name the kernel passes (=eth0), but can't find that
device for commands (since it changed it's name).
Instructing NetworkManager to ignore ifup-configured devices does not
help, since NetworkManager renames the devices and thus does not apply
/etc/network/interfaces rules for eth0.
Even worse: Even when listing the particular mac address in
/etc/NetworkManager/NetworkManager.conf to be ignored, NM ignores it in
the way that it does not configure it, but still renames it.
Is there any other way to make NetworkManager completely keep its dirty
fingers away from Network Devices except for completely killing it?
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Jan 19 11:16:42 2016
InstallationDate: Installed on 2015-09-03 (137 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
IpRoute:
default via 192.168.103.254 dev enp2s0 proto static metric 100
169.254.0.0/16 dev docker0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1
192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.102.125 metric 100
192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-01-19T11:01:36.653148
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
docker0 5b3eb2b2-d7bd-49a4-9b1d-32c6dbaaf121 bridge 1453198365 Di 19 Jan 2016 11:12:45 CET no 0 no /org/freedesktop/NetworkManager/Settings/1 yes docker0 activated /org/freedesktop/NetworkManager/ActiveConnection/0
Wired connection 1 c9b5bf9d-a9f7-4b15-a183-63209d80bf73 802-3-ethernet 1453198365 Di 19 Jan 2016 11:12:45 CET yes 0 no /org/freedesktop/NetworkManager/Settings/0 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug wily
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1535635
Title:
NetworkManager does not really ignore devices, disturbing udev
Status in network-manager package in Ubuntu:
New
Bug description:
Hi,
I'm just trying to configure an ubuntu machine to work as a network
controller (dhcp, dns,...) for several virtual and physical machines,
using a linux bridge as a virtual network, and trying to automatically
add USB-Ethernet-Devices to the bridge through udev.
Unfortunately my udev rules fail since Network Manager does rename new
Ethernet devices *before* udev runs, e.g.
eth0 to enx0000e80006d8
for my USB ethernet device. Thus, many regular udev rules fail since
they use the device name the kernel passes (=eth0), but can't find
that device for commands (since it changed it's name).
Instructing NetworkManager to ignore ifup-configured devices does not
help, since NetworkManager renames the devices and thus does not apply
/etc/network/interfaces rules for eth0.
Even worse: Even when listing the particular mac address in
/etc/NetworkManager/NetworkManager.conf to be ignored, NM ignores it
in the way that it does not configure it, but still renames it.
Is there any other way to make NetworkManager completely keep its
dirty fingers away from Network Devices except for completely killing
it?
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Jan 19 11:16:42 2016
InstallationDate: Installed on 2015-09-03 (137 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
IpRoute:
default via 192.168.103.254 dev enp2s0 proto static metric 100
169.254.0.0/16 dev docker0 scope link metric 1000
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1
192.168.100.0/22 dev enp2s0 proto kernel scope link src 192.168.102.125 metric 100
192.168.200.0/24 dev vlan0 proto kernel scope link src 192.168.200.1
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2016-01-19T11:01:36.653148
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
docker0 5b3eb2b2-d7bd-49a4-9b1d-32c6dbaaf121 bridge 1453198365 Di 19 Jan 2016 11:12:45 CET no 0 no /org/freedesktop/NetworkManager/Settings/1 yes docker0 activated /org/freedesktop/NetworkManager/ActiveConnection/0
Wired connection 1 c9b5bf9d-a9f7-4b15-a183-63209d80bf73 802-3-ethernet 1453198365 Di 19 Jan 2016 11:12:45 CET yes 0 no /org/freedesktop/NetworkManager/Settings/0 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1535635/+subscriptions
