Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
On Mon, 3 Sep 2018 12:54:30 +0200 Arian Sanusi wrote: > to put my paint point first, maybe it was not clear: at boot NM does not > connect at boot to a WiFi. Instead I have to click the applet, wait multiple > seconds for a scan to finish and then have to choose the wifi manually. NM > says it would be connected to my bridge, see attached screenshot. Does it work better if you create the bridge device with NM (i.e. remove it from /e/n/i) so the bridge and wifi device are both under NMs control? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
to put my paint point first, maybe it was not clear: at boot NM does not connect at boot to a WiFi. Instead I have to click the applet, wait multiple seconds for a scan to finish and then have to choose the wifi manually. NM says it would be connected to my bridge, see attached screenshot. > I still don't undestand: Are you saying that NM tries to manage your > "bridge" interface while it shouldn't? ^ this, at least sort of: it behaves like the presence of the bridge is enough, while the bridge can't give me internet access. It doesn't change bridge's settings AFAICT > Or are you expecting NM to manager your bridge interface but it does not? > Anyway, if want to mark a device as unmanaged by NM, you have more > explicit ways then relying on the eni parser. > E.g. you could create a conf file like this: > > # cat /etc/NetworkManager/conf.d/unmanaged.conf > [keyfile] > unmanaged-devices=interface-name:bridge thanks for this suggestion, I'll try it! however I still think theres something unnecessarily annoying that should be fixed, especially when docu suggest that ENI was enough. > I don't see anything in the logs which would indicate that NM manages > your bridge interface, it simply shows, that such a device has been > detected. the lines from the log that read wrong to me: > adding bridge port none to eni_ifaces none is a special value indicating an empty list that I guess the parser does not handle. If this was python it would be "bridge_ports = []" > devices added (path: /sys/devices/virtual/net/bridge, iface: bridge) > device added (path: /sys/devices/virtual/net/bridge, iface: bridge): > no ifupdown configuration found. I can't find another explanation for this as that the eni parser is wrong > device (bridge): Activation: starting connection 'bridge' > (92896f34-0c23-4893-a459-7bf9f941f397) if this is not saying that NM does something about the bridge, then it's misleading. signature.asc Description: OpenPGP digital signature
Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
On 9/2/18 00:43, Michael Biebl wrote: > On 9/1/18 23:58, Arian Sanusi wrote: >> I have these interfaces: >> "bridge": a bridge without any ports connected on start, LXCs connect here. >> It's configured in /etc/network/interfaces, and I expect NM not to touch it >> "mlan0": wifi, not in interfaces, expected to be handled by NM >> "lo": for completeness sake >> "eth0": not alway there (USB-interface) expected to be handled by NM. >> >> The one thing that's not as expected is that NM does regard "bridge" even >> though it should not. > > I still don't undestand: Are you saying that NM tries to manage your > "bridge" interface while it shouldn't? > Or are you expecting NM to manager your bridge interface but it does not? > > I don't see anything in the logs which would indicate that NM manages > your bridge interface, it simply shows, that such a device has been > detected. I'm not saying, the /etc/network/interfaces parser couldn't be improved (it's actually pretty shitty). That said, I'm not sure if your problem is really caused by that or if it's just a red herring. Anyway, if want to mark a device as unmanaged by NM, you have more explicit ways then relying on the eni parser. E.g. you could create a conf file like this: # cat /etc/NetworkManager/conf.d/unmanaged.conf [keyfile] unmanaged-devices=interface-name:bridge -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
On 9/1/18 23:58, Arian Sanusi wrote: > I have these interfaces: > "bridge": a bridge without any ports connected on start, LXCs connect here. > It's configured in /etc/network/interfaces, and I expect NM not to touch it > "mlan0": wifi, not in interfaces, expected to be handled by NM > "lo": for completeness sake > "eth0": not alway there (USB-interface) expected to be handled by NM. > > The one thing that's not as expected is that NM does regard "bridge" even > though it should not. I still don't undestand: Are you saying that NM tries to manage your "bridge" interface while it shouldn't? Or are you expecting NM to manager your bridge interface but it does not? I don't see anything in the logs which would indicate that NM manages your bridge interface, it simply shows, that such a device has been detected. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
I have these interfaces: "bridge": a bridge without any ports connected on start, LXCs connect here. It's configured in /etc/network/interfaces, and I expect NM not to touch it "mlan0": wifi, not in interfaces, expected to be handled by NM "lo": for completeness sake "eth0": not alway there (USB-interface) expected to be handled by NM. The one thing that's not as expected is that NM does regard "bridge" even though it should not. signature.asc Description: OpenPGP digital signature
Bug#907747: [Pkg-utopia-maintainers] Bug#907747: network-manager manages interface managed by /etc/network/interfaces
On 9/1/18 12:05, Arian Sanusi wrote: > Package: network-manager > Version: 1.12.2-2 > Severity: normal > > Dear Maintainer, > > I have a bridge configured by ifupdown in /etc/network/interfaces. Even > though NetworkManager.conf contains: > [ifupdown] > managed=false > > at boot Network-Manager often seems not to make an attempt of connecting to a > WiFi-AP which I think is a result of this. Could you be more specific about the problem. It's unclear to me, which interface you expect NetworkManager to manager and which not, and which interface exactly is not properly handled by NetworkManager. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#907747: network-manager manages interface managed by /etc/network/interfaces
Package: network-manager Version: 1.12.2-2 Severity: normal Dear Maintainer, I have a bridge configured by ifupdown in /etc/network/interfaces. Even though NetworkManager.conf contains: [ifupdown] managed=false at boot Network-Manager often seems not to make an attempt of connecting to a WiFi-AP which I think is a result of this. interfaces' bridge section: auto bridge iface bridge inet static bridge-ports none address 10.0.0.1/24 I think this might be due to "bridge-ports none" An extract of NetworkManager's log is attached - personal information was removed -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing'), (500, 'stable'), (400, 'unstable'), (300, 'experimental'), (1, 'experimental-debug') Architecture: arm64 (aarch64) Kernel: Linux 4.4.110-ARCH+ (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser3.117 ii dbus 1.12.10-1 ii libaudit1 1:2.8.3-1+b1 ii libbluetooth3 5.50-1 ii libc6 2.27-5 ii libcurl3-gnutls7.61.0-1 ii libglib2.0-0 2.56.1-2 ii libgnutls303.5.19-1 ii libjansson42.11-1 ii libmm-glib01.7.990-1 ii libndp01.6-1+b1 ii libnewt0.520.52.20-6 ii libnm0 1.12.2-2 ii libpam-systemd 239-7 ii libpolkit-agent-1-00.105-21 ii libpolkit-gobject-1-0 0.105-21 ii libpsl50.20.2-1 ii libreadline7 7.0-5 ii libselinux12.8-1+b1 ii libsystemd0239-7 ii libteamdctl0 1.27-1 ii libudev1 239-7 ii libuuid1 2.32.1-0.1 ii lsb-base 9.20170808 ii policykit-10.105-21 ii udev 239-7 ii wpasupplicant 2:2.6-18 Versions of packages network-manager recommends: pn crda pn dnsmasq-base ii iptables 1.6.2-1.1 ii isc-dhcp-client 4.3.5-4+b1 pn modemmanager pn ppp Versions of packages network-manager suggests: pn libteam-utils -- no debconf information systemd[1]: Starting Network Manager... NetworkManager (version 1.12.2) is starting... (for the first time) Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) systemd[1]: Started Network Manager. bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" manager[0x58a710e020]: monitoring kernel firmware directory '/lib/firmware'. monitoring ifupdown state file '/run/network/ifstate'. hostname: hostname: using hostnamed hostname: hostname changed from (none) to "kevin23" dns-mgr[0x58a7117910]: init: dns=default, rc-manager=resolvconf rfkill0: found WiFi radio killswitch (at /sys/devices/platform/f800.pcie/pci:00/:00:00.0/:01:00.0/ieee80211/phy0/rfkill0) (driver mwifiex_pcie) manager[0x58a710e020]: rfkill: WiFi hardware radio set enabled manager[0x58a710e020]: rfkill: WWAN hardware radio set enabled init! interface-parser: parsing file /etc/network/interfaces interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d interface-parser: finished parsing file /etc/network/interfaces found bridge ports none for bridge adding bridge port none to eni_ifaces management mode: unmanaged devices added (path: /sys/devices/platform/f800.pcie/pci:00/:00:00.0/:01:00.0/net/mlan0, iface: mlan0) device added (path: /sys/devices/platform/f800.pcie/pci:00/:00:00.0/:01:00.0/net/mlan0, iface: mlan0): no ifupdown configuration found. devices added (path: /sys/devices/virtual/net/bridge, iface: bridge) device added (path: /sys/devices/virtual/net/bridge, iface: bridge): no ifupdown configuration found. devices added (path: /sys/devices/virtual/net/lo, iface: lo) device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. end _init. settings: Loaded settings plugin: SettingsPluginIfupdown (/usr/lib/aarch64-linux-gnu/NetworkManager/1.12.2/libnm-settings-plugin-ifupdown.so) settings: Loaded settings plugin: NMSKeyfilePlugin (internal) (-1492008384) ... get_connections. (-1492008384) ... get_connections (managed=false): return empty list. get unmanaged devices count: 0 manager: rfkill: WiFi enabled by radio killswitch; enabled by state file manager: rfkill: WWAN enabled by radio killswitch; enabled by state file manager: Networking is enabled by state file dhcp-init: Using DHCP client 'dhclient' Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.12.2/libnm-device-plugin-team.so) Loaded device plugin: NMBluezManager (/us
