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