On Thu, 07 May 2015 02:30:16 +0200 Michael Biebl <bi...@debian.org>
wrote:
> Am 07.05.2015 um 01:55 schrieb Michael Biebl:
> > Am 07.05.2015 um 01:32 schrieb Andrea Capriotti:
> >> On Thu, 07 May 2015 01:09:53 +0200 Michael Biebl
<bi...@debian.org> wrote:
> >>> Control: tags -1 moreinfo
> >>>
> >>> Please provide more informatin about your network setup:
> >>> a/ which interfaces are managed by NM, which are managed
elsewhere
> >>> (ifupdown)
> >>> b/ please provide a verbose debug log of NetworkManager
> >>
> >> Same problem here.
> >>
> >> # grep resolvconf /var/log/syslog
> >> May 7 01:16:15 nb-capriotti NetworkManager[13437]: <warn> could
not commit DNS changes: /sbin/resolvconf is not executable
> >>
> >> I fixed it installing resolvconf.
> >
> > That's not a fix. Please provide the information I requested.
> > Maybe that provides some hint's what's going wrong.
> > Do you have any custom configuration in
> > /etc/NetworManager/NetworkManager.conf?
>
> I think I tracked this down.
>
> The Debian package builds with resolvconf support, in case users
decide
> to install resolvconf.
> Due to this commit [1], this makes NM now assume that resolvconf is
also
> available during runtime, which is not the case by default on Debian.
> That's obviously wrong.
> NM should fallback to non-resolvconf mode, if the resolvconf binary
was
> not found during runtime.
This is consistent with what I am seeing. Also, this may be of
interest to you, there is a file /etc/resolv.conf.tmp on my system when
resolvconf is not installed:
# Generated by NetworkManager
nameserver 192.168.1.1
Yet another workaround seems to be to copy this file over to
/etc/resolv.conf to get temporary internet access to install resolvconf
(if it is not in your apt cache).
Best regards,
--
Cameron Norman
