Bug#934690: networkmanager does not parse interface config file correctly
On Mi, 14 aug 19, 15:18:15, Hans-Cees Speel wrote: > On 13-08-19 21:15, andreimpope...@gmail.com wrote: > > > > Raspbian is making several changes compared to a pristine Debian system. > > Combine this with images being produced by third parties, with possible > > additional customizations and it becomes impossible to diagnoze an issue > > from Debian perspective. > > > > Please kindly report bugs in Debian only if you can reproduce the > > behaviour with a pure Debian install. > > > > I would suggest you contact Raspbian support channels to find a solution > > to your problem and if this is indeed a bug report it to Raspbian. > > While I respect your difficulties from the debian perspective: Please note I'm only triaging bugs filed against unknown packages. > * some more info would be welcome. Is my assertion correct that given >my configuration file form netwerokmanager resolv.conf should only >have one dns-address. If this is not the case my and your time is >wasted to find out more The file /etc/resolvconf/resolv.conf.d/head in Debian stretch looks like this: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN You can verify that yourself by downloading the package from a Debian mirror and inspecting it, e.g. with mc. It seems like your issue is due to a Raspbian and/or image specific customization. Hope this helps, Andrei -- Looking after bugs reported against inexistent or removed packages signature.asc Description: PGP signature
Bug#934690: networkmanager does not parse interface config file correctly
Package: networkmanager Version: 1.6.2 Severity: normal Dear Maintainer, Hello, I am using raspbian (debian based) PRETTY_NAME="Debian GNU/Linux 9 (stretch)" trying to switch from dhcp to a static IP. But dns config changes keep on failing to do so I have the config files below I would suspect networkmanager would thus: * manage the file /etc/resolvconf/run/resolv.conf * to read *ONLY* the dns-server 192.168.0.112 However, some (probably systemd?) proces also adds 8.8.8.8 I suspect because this file contains that server: root@bananas:~# cat /etc/resolvconf/resolv.conf.d/head nameserver 8.8.8.8 Because the resolv.conf file holds *TWO* dns-severs, and I did not congifure 8.8.8.8: root@bananas:~# cat /etc/resolvconf/run/resolv.conf nameserver 8.8.8.8 nameserver 192.168.0.112 I was wondering if this is a bug in networkmanager? Should it not make sure resolv.conf reflects its configfiles? Thanks. root@bananas:~# nmcli d DEVICE TYPE STATE CONNECTION eth0 ethernet connected eth0 bond0 bond unmanaged -- dummy0 dummy unmanaged -- lo loopback unmanaged -- root@bananas:~# nmcli c NAME UUID TYPE DEVICE eth0 89f35383-2b42-4bec-8220-e4db54512147 802-3-ethernet eth0 Ifupdown (eth0) 681b428f-beaf-8932-dce4-687ed5bae28e 802-3-ethernet -- root@bananas:~# cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile [ifupdown] managed=true root@bananas:~# cat /etc/network/interfaces # Include additional interface stanzas. source-directory interfaces.d # The loopback network interface auto lo iface lo inet loopback # eth0 network interface auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.83 gateway 192.168.0.111 netmask 255.255.255.0 dns-nameservers 192.168.0.112 iface eth0 inet6 manual pre-down ip -6 addr flush dev $IFACE
