Package: network-manager Version: 0.9.10.0-7 Severity: normal Tags: ipv6 I have defined the following NetworkManager wired connection:
[ethernet] duplex=full [connection] id=Wired connection 1 type=ethernet [ipv6] method=auto dns=2a00:e10:1000:10:4386:102:67:53; ip6-privacy=1 [ipv4] method=auto dns=78.138.102.67; Before connecting to the network the /etc/resolv.conf looks like: $ cat /etc/resolv.conf # Generated by NetworkManager Just after connecting to the network the file looks like: $ cat /etc/resolv.conf # Generated by NetworkManager search cm.cablesurf.de cm.cablesurf.de. nameserver 195.234.128.12 nameserver 195.234.128.9 nameserver 78.138.102.67 # NOTA: el resolutor de nombres de libc puede que no soporte más de 3 servidores de nombres. # Puede que los servidores de nombres listados abajo no se reconozcan. nameserver 2001:4c50:6:4000::12 nameserver 2001:4c50:6:4000::16 nameserver 2a00:e10:1000:10:4386:102:67:53 This is just fine, but only 10 seconds after that the file now looks like: $ cat /etc/resolv.conf nameserver 2001:4c50:6:4000::12 nameserver 2001:4c50:6:4000::16 and the IPv4 server has dissapeared together with the custom additional nameservers. Looking at journalctl I can see that this happens just after NetworkManager renews the DHCPv6 leasing: ene 16 22:14:19 NetworkManager[799]: <info> domain search 'cm.cablesurf.de.' ene 16 22:14:19 NetworkManager[799]: <info> nameserver '2001:4c50:6:4000::16' ene 16 22:14:19 NetworkManager[799]: <info> nameserver '2001:4c50:6:4000::12' ene 16 22:14:19 NetworkManager[799]: <info> address 2001:4c50:2cd:1400:5e26:aff:fe7e:b485 ene 16 22:14:19 NetworkManager[799]: <info> preferred_lft 30 ene 16 22:14:19 NetworkManager[799]: <info> valid_lft 60 ene 16 22:14:19 NetworkManager[799]: <info> (eth0): DHCPv6 state changed renew6 -> renew6 ene 16 22:14:19 dhclient[32373]: RCV: Reply message on eth0 from fe80::c627:95ff:feb0:f03. ene 16 22:14:19 dhclient[32373]: XMT: Renew on eth0, interval 9520ms. ene 16 22:14:19 dhclient[32373]: PRC: Renewing lease on eth0. The DHCPv4 leasing is on the other hand every 100000 seconds, which is the value I set up in my router. For some reason the router doesn´t honor that value for IPv6 leases. The fact that NetworkManager modifies the DNS resolver is causing problems since the IPv6 resolvers are much slower and I loose the custom resolvers. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (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.113+nmu3 ii dbus 1.8.20-0+deb8u1 ii init-system-helpers 1.22 ii isc-dhcp-client 4.3.1-6 ii libc6 2.19-18+deb8u1 ii libdbus-1-3 1.8.20-0+deb8u1 ii libdbus-glib-1-2 0.102-1 ii libgcrypt20 1.6.3-2 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-28 3.3.8-6+deb8u3 ii libgudev-1.0-0 215-17+deb8u2 ii libmm-glib0 1.4.0-1 ii libndp0 1.4-2 ii libnewt0.52 0.52.17-1+b1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnm-glib4 0.9.10.0-7 ii libnm-util2 0.9.10.0-7 ii libpam-systemd 215-17+deb8u2 ii libpolkit-gobject-1-0 0.105-8 ii libreadline6 6.3-8+b3 ii libsoup2.4-1 2.48.0-1 ii libsystemd0 215-17+deb8u2 ii libteamdctl0 1.12-2 ii libuuid1 2.25.2-6 ii lsb-base 4.1+Debian13+nmu1 ii policykit-1 0.105-8 ii udev 215-17+deb8u2 ii wpasupplicant 2.3-1+deb8u3 Versions of packages network-manager recommends: ii crda 3.13-1 ii dnsmasq-base 2.72-3+deb8u1 ii iptables 1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager 1.4.0-1 ii ppp 2.4.6-3.1 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.31-5 pn libteam-utils <none> -- no debconf information