Your message dated Thu, 15 Aug 2019 15:08:57 +0200 with message-id <e64bbc95-6fff-c298-6998-54c474a61...@debian.org> and subject line Re: [Pkg-utopia-maintainers] Bug#934694: [bananas.hanscees.com] network-manager: networkmanager perhaps does not parse dns-server in interface config file correctly has caused the Debian Bug report #934694, regarding [bananas.hanscees.com] network-manager: networkmanager perhaps does not parse dns-server in interface config file correctly to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 934694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: network-manager Version: 1.6.2-3+deb9u2 Severity: normal Dear Maintainer, Bug description: 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 The config files I am using that configure static ip and an dns-server are 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 126.96.36.199 I suspect because on debian this file (which I did not alter) contains the 188.8.131.52 dns server: root@bananas:~# cat /etc/resolvconf/resolv.conf.d/head nameserver 184.108.40.206 Anyway, after I configured only 1 dns-server and a reboot the resolv.conf file falsely now holds *TWO* dns-severs, and I did not configure 220.127.116.11: Here is that file root@bananas:~# cat /etc/resolvconf/run/resolv.conf nameserver 18.104.22.168 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 O*** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: armhf (armv7l) Kernel: Linux 4.19.62-sunxi (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8), LANGUAGE=en_US.UTF-8 (charmap=locale: Cannot set LC_ALL to default locale: No such file or directory UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser 3.115 ii dbus 1.10.28-0+deb9u1 ii init-system-helpers 1.48 ii libaudit1 1:2.6.7-2 ii libbluetooth3 5.43-2+deb9u1 ii libc6 2.24-11+deb9u4 ii libglib2.0-0 2.50.3-2 ii libgnutls30 3.5.8-5+deb9u4 ii libgudev-1.0-0 230-3 ii libjansson4 2.9-1 ii libmm-glib0 1.6.4-1 ii libndp0 1.6-1+b1 ii libnewt0.52 0.52.19-1+b1 ii libnl-3-200 3.2.27-2 ii libnm0 1.6.2-3+deb9u2 ii libpam-systemd 232-25+deb9u11 ii libpolkit-agent-1-0 0.105-18+deb9u1 ii libpolkit-gobject-1-0 0.105-18+deb9u1 ii libreadline7 7.0-3 ii libselinux1 2.6-3+b3 ii libsoup2.4-1 2.56.0-2+deb9u2 ii libsystemd0 232-25+deb9u11 ii libteamdctl0 1.26-1+b1 ii libuuid1 2.29.2-1+deb9u1 ii lsb-base 9.20161125 ii policykit-1 0.105-18+deb9u1 ii udev 232-25+deb9u11 ii wpasupplicant 2:2.4-1+deb9u4 Versions of packages network-manager recommends: ii crda 3.18-1 pn dnsmasq-base <none> ii iptables 1.6.0+snapshot20161117-6 ii iputils-arping 3:20161105-1 ii isc-dhcp-client 4.3.5-3+deb9u1 pn modemmanager <none> pn ppp <none> Versions of packages network-manager suggests: pn libteam-utils <none> -- Configuration Files: /etc/NetworkManager/NetworkManager.conf changed [not included] -- debconf information excluded
--- End Message ---
--- Begin Message ---Am 13.08.19 um 16:36 schrieb hanscees: > Package: network-manager > Version: 1.6.2-3+deb9u2 > Severity: normal > > Dear Maintainer, > > > Bug description: > 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 > > The config files I am using that configure static ip and an dns-server are > 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 22.214.171.124 > I suspect because on debian this file (which I did not alter) contains the > 126.96.36.199 dns server: > > root@bananas:~# cat /etc/resolvconf/resolv.conf.d/head > nameserver 188.8.131.52 > > Anyway, after I configured only 1 dns-server and a reboot the resolv.conf > file falsely now holds *TWO* dns-severs, and I did not > configure 184.108.40.206: > > Here is that file > root@bananas:~# cat /etc/resolvconf/run/resolv.conf > nameserver 220.127.116.11 > 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? Since you are using resolvconf and resolv.conf.d/head contains "nameserver 18.104.22.168" the resulting resolv.conf looks correct. If you don't want resolvconf to add 22.214.171.124 remove this entry or don't use resolvconf. The latter you can do by either uninstalling resolvconf or by configuring network-manager to not use resolvconf (the default NM is to use resolvconf if installed). Fwiw, I have no idea who/what put 126.96.36.199 in /etc/resolvconf/resolv.conf.d/head. It's most likely a raspbian default. If you think this is a bad default, you should ping the raspbian folks about this.
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________ Pkg-utopia-maintainers mailing list Pkgemail@example.com https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers