Package: network-manager
Version: 1.6.2-3
Severity: important
Tags: upstream
Dear everyone,
I would like to ask help configuring second IP address on debian 9.3 with
Network Manager because I found a malfunction.
Since it seems to me I found a bug I will give lot of details.
Information regarding to the OS are the followings:
OS: Debian 9.3 64 bit
kernel: 4.9.0-6-amd64
NetworkManager version is: 1.6.2
DNS software: bind9
Bind9 version: 9.10.3.dfsg.P4-12.3+deb9u4
My plan is to give a second IP address to my physical interface card with
Network Manager. There is only one physical interface card currently in the
machine.
The card gets currently it's details through DHCP from the router by IP
address-MAC address bonding except for the DNS settings because that is
prohibited on client side and set manually to 127.0.0.1. The manually set DNS
is important part of this situation because as I make the second IP address
accessible on the card the DNS (which is provided by bind9) stops resolving the
local but even the internet-available records.
Let's see the details in a before and after change scope and of course how I
change the settings:
I,
The IP addresses of the machine are the followings:
root@lx-hp:~# ip a | grep 'inet '
inet 127.0.0.1/8 scope host lo
inet 192.168.0.104/24 brd 192.168.0.255 scope global dynamic enp0s25
root@lx-hp:~#
The DNS settings are the followings:
root@lx-hp:~# cat /etc/resolv.conf
# Generated by NetworkManager
search foo.foo2.hu
nameserver 127.0.0.1
root@lx-hp:~#
There is only one connection definied currently:
root@lx-hp:~# nmcli con show
NAME UUID TYPE DEVICE
main_interface 61303e01-36ee-494a-bbcb-6da375abf389 802-3-ethernet enp0s25
root@lx-hp:~#
The physical interface card settings are the followings:
root@lx-hp:~# cat /etc/NetworkManager/system-connections/main_interface
[connection]
id=main_interface
uuid=61303e01-36ee-494a-bbcb-6da375abf389
type=802-3-ethernet
[802-3-ethernet]
[ipv4]
method=auto
ignore-auto-dns=true
dns=127.0.0.1
[ipv6]
method=auto
ip6-privacy=2
root@lx-hp:~#
DNS lookup works correctly with these settings:
root@lx-hp:~# nslookup mail.google.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
mail.google.com canonical name = googlemail.l.google.com.
Name: googlemail.l.google.com
Address: 172.217.16.101
root@lx-hp:~#
192.168.0.109 is not used IP address in my network:
root@lx-hp:~# ping 192.168.0.109
PING 192.168.0.109 (192.168.0.109) 56(84) bytes of data.
^C
--- 192.168.0.109 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1007ms
root@lx-hp:~#
II, Changing the settings:
As I am not sure about the config directives of debian based NetworkManager I
used nmtui.
See the picture below.
The configuration file looked like the followings:
root@lx-hp:~# cat /etc/NetworkManager/system-connections/main_interface
[connection]
id=main_interface
uuid=61303e01-36ee-494a-bbcb-6da375abf389
type=ethernet
permissions=
timestamp=1521121495
[ethernet]
mac-address-blacklist=
[ipv4]
address1=192.168.0.104/24
address2=192.168.0.109/24
dns=127.0.0.1;
dns-search=
ignore-auto-dns=true
method=manual
[ipv6]
addr-gen-mode=eui64
dns-search=
ip6-privacy=2
method=auto
root@lx-hp:~#
III,
To get effect for sure, I rebooted the machine, and afterwards the followings
are in effect:
The IP addresses are configured:
root@lx-hp:~# ip a | grep -i 'inet '
inet 127.0.0.1/8 scope host lo
inet 192.168.0.104/24 brd 192.168.0.255 scope global enp0s25
inet 192.168.0.109/24 brd 192.168.0.255 scope global secondary enp0s25
root@lx-hp:~#
Both IP address are pingable from my host:
root@lx-hp:~# ping 192.168.0.104
PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data.
64 bytes from 192.168.0.104: icmp_seq=1 ttl=64 time=0.033 ms
64 bytes from 192.168.0.104: icmp_seq=2 ttl=64 time=0.023 ms
^C
--- 192.168.0.104 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1010ms
rtt min/avg/max/mdev = 0.023/0.028/0.033/0.005 ms
root@lx-hp:~# ping 192.168.0.109
PING 192.168.0.109 (192.168.0.109) 56(84) bytes of data.
64 bytes from 192.168.0.109: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 192.168.0.109: icmp_seq=2 ttl=64 time=0.027 ms
^C
--- 192.168.0.109 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1018ms
rtt min/avg/max/mdev = 0.027/0.029/0.031/0.002 ms
root@lx-hp:~#
But the local DNS server stopped working:
root@lx-hp:~# nslookup mail.google.com
Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find mail.google.com: SERVFAIL
root@lx-hp:~#
However the interface card works perfectly with the two IP addresses. It is
pingable from another host also:
root@lx-raspberry:~# ping 192.168.0.104
PING 192.168.0.104 (192.168.0.104) 56(84) bytes of data.
64 bytes from 192.168.0.104: icmp_seq=1 ttl=64 time=0.584 ms
64 bytes from 192.168.0.104: icmp_seq=2 ttl=64 time=0.611 ms
64 bytes from 192.168.0.104: icmp_seq=3 ttl=64 time=0.348 ms
^C
--- 192.168.0.104 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.348/0.514/0.611/0.119 ms
root@lx-raspberry:~#
root@lx-raspberry:~# ping 192.168.0.109
PING 192.168.0.109 (192.168.0.109) 56(84) bytes of data.
64 bytes from 192.168.0.109: icmp_seq=1 ttl=64 time=1.12 ms
64 bytes from 192.168.0.109: icmp_seq=2 ttl=64 time=0.365 ms
64 bytes from 192.168.0.109: icmp_seq=3 ttl=64 time=0.581 ms
^C
--- 192.168.0.109 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.365/0.689/1.121/0.317 ms
So do you have any idea what should I change to avoid the DNS malfunction?
Or can you examine if this happening is a bug in NetworkManager?
Thank you!
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.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 adduser 3.115
ii dbus 1.10.24-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+deb9u1
ii libglib2.0-0 2.50.3-2
ii libgnutls30 3.5.8-5+deb9u3
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
ii libpam-systemd 232-25+deb9u1
ii libpolkit-agent-1-0 0.105-18
ii libpolkit-gobject-1-0 0.105-18
ii libreadline7 7.0-3
ii libselinux1 2.6-3+b3
ii libsoup2.4-1 2.56.0-2+deb9u1
ii libsystemd0 232-25+deb9u1
ii libteamdctl0 1.26-1+b1
ii libuuid1 2.29.2-1+deb9u1
ii lsb-base 9.20161125
ii policykit-1 0.105-18
ii udev 232-25+deb9u1
ii wpasupplicant 2:2.4-1+deb9u1
Versions of packages network-manager recommends:
ii crda 3.18-1
ii dnsmasq-base 2.76-5+deb9u1
ii iptables 1.6.0+snapshot20161117-6
ii iputils-arping 3:20161105-1
ii isc-dhcp-client 4.3.5-3+deb9u1
ii modemmanager 1.6.4-1
ii ppp 2.4.7-1+4
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- no debconf information
