however, when I check:
systemd-resolve --status
I get this:
Global172,in-addr.
DNS DOmain: dhcp.inet.fi
DNSSEC NTA: 10.in-add.arpa
16.172.in-addr.arpa
168.192.in-add.arpa
.
.
.
.
Link 3 (WLP4s0)
Current Scopes: DNS
This is not working in ubuntu gnome:
network-manager 1.4.4-1ubuntu3
network-manager-gnome 1.4.2-1ubuntu4
in /var/log/syslog
I get lots of Error Messages after nm-dispatcher: req:3 'up' [wlp4s0]: start
running ordered scripts...
systemd-resolved[1104]: Switching to DNS server 192.168.55.5 for
This bug is now solved with the latest network-manager v. 1.4.2-3ubuntu2 in
Zesty.
Here:
https://launchpad.net/ubuntu/+source/network-manager/1.4.2-3ubuntu2
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
I can also confirm, though there is no need to, that the newest version of NM
1.4.2-3ubuntu1 does not work better either.
So this bug still remains unsolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First of all,
If NM 1.4.2-2ubuntu4 needs the package resolvconf in order to function
properly, it should depend on it.
Secondly,
NM 1.4.2-2ubuntu3 works perfectly, like all earlier versions, without the
package resolvconf.
Thirdly,
after installing resolvconf with NM 1.4.2-2ubuntu4, NM still
On Wed, Dec 07, 2016 at 09:34:43PM -, Martin Pitt wrote:
> Ah, so you didn't have resolvconf installed (and therefore also not
> ubuntu-minimal), that's a good data point, thank you! This should be
> part of this bug -- NM should get along with this better.
Removing ubuntu-minimal is always
Ah, so you didn't have resolvconf installed (and therefore also not
ubuntu-minimal), that's a good data point, thank you! This should be
part of this bug -- NM should get along with this better.
Do you see the search domain in "systemd-resolve --status"?
--
You received this bug notification
One possible issue is the contents of the /etc/resolv.conf (or actually
/run/resolvconf/resolv.conf).
With NM 1.4.2-2ubuntu4 the /etc/resolv.conf is:
nameserver 127.0.0.53
But with NM 1.4.2-2ubuntu3 it is:
search dhcp.inet.fi
nameserver 127.0.1.1
So where did the line "search dhcp.inet.fi"
And a little more info:
"/etc/NetworkManager/NetworkManager.conf"
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
"/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
Martin,
I installed the package resolvconf.
Now the command gives this:
"systemctl status resolvconf"
● resolvconf.service - Nameserver information manager
Loaded: loaded (/lib/systemd/system/resolvconf.service; enabled; vendor
preset: enabled)
Active: active (exited) since Wed 2016-12-07
That is simply:
"Unit resolvconf.service could not be found"
I believe there is some package(s) that I do not have installed, but I
should have?
NM 1.4.2-2ubuntu4 needs something to be installed, that NM
1.4.2-2ubuntu3 did not need.
--
You received this bug notification because you are a
What does "systemctl status resolvconf" say? is it not running for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647133
Title:
dns=dnsmasq does not work any more
To manage notifications
Martin,
The /etc/resolv.conf in my set up is really a link.
The target is (where folder "var/run" is a link to the folder "run"):
/var/run/NetworkManager/resolv.conf
However, I upgraded NM to the version 1.4.2-2ubuuntu4 and run the following 4
commands:
sudo systemctl stop NetworkManager
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647133
Title:
dns=dnsmasq does not work any more
To manage notifications about this bug go to:
> # Generated by NetworkManager
> nameserver 127.0.1.1
OK, that's definitively unexpected. It looks like NM is still using a
different plugin for managing /etc/resolv.conf and that thinks it's
using the dnsmasq plugin (127.0.1.1) while not actually starting
dnsmasq. That part is understood and
Martin,
OK, here goes:
cat /etc/resolv.conf
# Generated by NetworkManager
search dhcp.inet.fi
nameserver 127.0.1.1
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
journalctl -u NetworkManager.service -u systemd-resolved.service -b >
OK, thanks. I'm afraid I need the NM log and /etc/resolv.conf with NM
1.4.2-2ubuntu4 without "dns=dnsmasq".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647133
Title:
dns=dnsmasq does not work
Martin,
I removed the line "dns=dnsmasq"
from the conf file.
Then upgraded to NM 1.4.2-2ubuntu4
Rebooted and checked that dns=dnsmasq was absent from the conf file. It was.
However, the result was still the same = no network.
Downgraded back to NM 1.4.2-2ubuntu3, got the network back and fine.
18 matches
Mail list logo
