Hi, Since this does not have private info, let's keep this in public so we do not loose this.
On Thu, Jul 02, 2015 at 10:34:47AM +0200, Andreas Glaeser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sat, 27 Jun 2015 18:33:50 +0900 > Osamu Aoki <[email protected]> wrote: > > > Hi, > > > > FYI: > > > > Here are things I should read .... first the upstream. > > > > http://www.freedesktop.org/software/systemd/man/resolved.conf.html > > > > http://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html > > > > Here are the interesting summary overview: > > https://github.com/lnussbaum/slides-lectures/raw/master/systemd.pdf > > > > Also, this gives me interesting readings: > > http://planet-search.debian.org/cgi-bin/search.cgi?terms=systemd > > > > Osamu > > > > Hello again, > > today I tried it with resolvconf and I can confirm, that it works partially > at least: > > > andrew@s55:~$ sudo aptitude install resolvconf > > The following NEW packages will be installed: > > resolvconf > > 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > > Need to get 78.1 kB of archives. After unpacking 285 kB will be used. > > Get: 1 http://ftp.tu-chemnitz.de/pub/linux/debian/debian/ jessie/main > > resolvconf all > > 1.76.1 [78.1 kB] Fetched 78.1 kB in 0s (369 kB/s) > > Preconfiguring packages ... > > Selecting previously unselected package resolvconf. > > (Reading database ... 244174 files and directories currently installed.) > > Preparing to unpack .../resolvconf_1.76.1_all.deb ... > > Unpacking resolvconf (1.76.1) ... > > Processing triggers for man-db (2.7.0.2-5) ... > > Processing triggers for systemd (215-17+deb8u1) ... > > Setting up resolvconf (1.76.1) ... > > Processing triggers for systemd (215-17+deb8u1) ... > > Processing triggers for resolvconf (1.76.1) ... > > > > andrew@s55:~$ sudo nano /etc/network/interfaces > > andrew@s55:~$ sudo service networking restart > > andrew@s55:~$ cat /etc/resolv.conf > > # 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 > > nameserver 192.168.0.108 > > nameserver 2a02:8109:9ac0:2354::1 > > andrew@s55:~$ cat /etc/network/interfaces > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > > > iface lo inet loopback > > > > # The primary network interface > > > > auto eth1 > > > > allow-hotplug eth1 > > > > #iface eth0 inet manual > > > > iface eth1 inet static > > address 192.168.0.60 > > netmask 255.255.255.0 > > gateway 192.168.0.1 > > dns-nameservers 192.168.0.108 > > > > This means, that installing resolvconf correctly overrides systemd's > symlink on /etc/resolv.conf, but I have two nameserver-entries in the > file now, my local dns-cache and the IP6-representation of the > standard gateway. I have to deal with resolvconf-configuration in > order to remove the default there. > > Because /etc/resolv.conf cannot be edited manually anymore, this > wiki-page also needs updating for Jessie: > https://wiki.debian.org/HowTo/dnsmasq Probably also some others. As > stated from the systemd-mainainers, it is not possible to go in a > mixed manner, having just DNS configured via systemd, not the other > networking, but one has to abandon ifup/down and do all the > networking-configuration with systemd, if resolvconf doesn't come > handy for your needs. Hope this helps. > > Greetings > > Andreas > > P.S. There is also something else, where systemd has to be paid > regards to, namely disabling the bridge-netfilter, see > > $ man sysctl.d > > This also doesn't work anymore by just making the entries in > sysctl.conf, but it will probably be disabled by default in the > future. Anyway, if there is an issue with the old resolvconf (Which I do not have it installed any more as I checked), you should talk to its maintainer. Thomas Hood is very much available for such discussion. Check the BTS before contacting your issue. Osamu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
