Ubuntu
network-manager package

accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)

Bug #1650927 reported by ernsteiswuerfel
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Access to local ethernet is possible (e.g. ping 192.168.2.2), access to internet is not possible:
ping: ports.ubuntu.com: Name or service not known
ping: www.google.com: Name or service not known

It does not matter if my PowerBook G4 is connected via WLAN or ethernet, the effect is the same.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.2-2ubuntu4
ProcVersionSignature: Ubuntu 4.9.0-11.12-powerpc-smp 4.9.0
Uname: Linux 4.9.0-11-powerpc-smp ppc
ApportVersion: 2.20.4-0ubuntu1
Architecture: powerpc
CasperVersion: 1.379
Date: Thu Nov 3 18:13:07 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.3.1 dev wlP1p17s0 proto static metric 600
 169.254.0.0/16 dev wlP1p17s0 scope link metric 1000
 192.168.3.0/24 dev wlP1p17s0 proto kernel scope link src 192.168.3.2 metric 600
LiveMediaBuild: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161218)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile

 [ifupdown]
 managed=false
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 802-11-wireless 1478196808 Thu 03 Nov 2016 06:13:28 PM UTC yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlP1p17s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4
 Wired connection 1 1a0d2e10-42f2-3154-b4f6-dfbec067bff3 802-3-ethernet 1478196172 Thu 03 Nov 2016 06:02:52 PM UTC yes 4294966297 no /org/freedesktop/NetworkManager/Settings/0 no -- -- --
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlP1p17s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Carcosa 82f9a6ba-8a34-4aa8-8bba-6520f8b73c62 /org/freedesktop/NetworkManager/ActiveConnection/4
 enP2p36s15f0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.4.2 connected started full enabled enabled enabled enabled enabled

Revision history for this message
ernsteiswuerfel (erhard-f) wrote :
summary: - although network interface is up a connection to internet cannot be
- established
+ accessing local ethernet is possible, accessing internet is not possible
+ (Ubuntu MATE 17.04, ppc)
Revision history for this message
ernsteiswuerfel (erhard-f) wrote :
Download full text (5.8 KiB)

Some "journalctl -k"-output, getting a lots of "DNSSEC validation failed"-errors:

Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question com IN DNSKEY: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question com IN DS: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question . IN DNSKEY: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question daisy.ubuntu.com IN A: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question daisy.ubuntu.com IN SOA: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question daisy.ubuntu.com IN DS: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question ubuntu.com IN SOA: signature-expired
Nov 03 19:24:05 ubuntu-mate whoopsie[2004]: [19:24:05] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0
Nov 03 19:24:05 ubuntu-mate whoopsie[2004]: [19:24:05] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0
Nov 03 19:24:05 ubuntu-mate whoopsie[2004]: [19:24:05] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0
Nov 03 19:24:05 ubuntu-mate dbus-daemon[3146]: Activating service name='org.freedesktop.Notifications'
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question ubuntu.com IN DS: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question com IN DNSKEY: signature-expired
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question com IN DS: signature-expired
Nov 03 19:24:05 ubuntu-mate whoopsie[2004]: [19:24:05] Cannot reach: https://daisy.ubuntu.com
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: DNSSEC validation failed for question . IN DNSKEY: signature-expired
Nov 03 19:24:05 ubuntu-mate nm-dispatcher[4623]: req:2 'up' [wlP1p17s0]: start running ordered scripts...
Nov 03 19:24:05 ubuntu-mate avahi-daemon[2034]: Registering new address record for fe80::923:f762:65ee:a8b5 on wlP1p17s0.*.
Nov 03 19:24:05 ubuntu-mate avahi-daemon[2034]: New relevant interface wlP1p17s0.IPv6 for mDNS.
Nov 03 19:24:05 ubuntu-mate avahi-daemon[2034]: Joining mDNS multicast group on interface wlP1p17s0.IPv6 with address fe80::923:f762:65ee:a8b5.
Nov 03 19:24:05 ubuntu-mate nm-dispatcher[4623]: req:2 'up' [wlP1p17s0]: new request (3 scripts)
Nov 03 19:24:05 ubuntu-mate nm-dispatcher[4623]: req:1 'connectivity-change': start running ordered scripts...
Nov 03 19:24:05 ubuntu-mate nm-dispatcher[4623]: req:1 'connectivity-change': new request (3 scripts)
Nov 03 19:24:05 ubuntu-mate systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 03 19:24:05 ubuntu-mate dbus[1946]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Nov 03 19:24:05 ubuntu-mate systemd-resolved[2632]: Switching to DNS server 192.168.3.1 for interface wlP1p17s0.
Nov 03 19:24:05 ubuntu-mate NetworkManager[2012]: <info> ...

Read more...

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1650927

tags: added: iso-testing
Revision history for this message
ernsteiswuerfel (erhard-f) wrote :

Tested todays daily iso (2017-02-02), can't reproduce this bug.

Changed in network-manager (Ubuntu):
status: New → Invalid
Revision history for this message
mikewhatever (mikewhatever) wrote :

Reproducible on MATE 17.04 amd64, also reported by others:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1681597
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499

Suggested workaround is to "put 'DNSSEC=off' in /etc/systemd/resolved.conf".

Changed in network-manager (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Marzanna (marzanna) wrote :

In Xubuntu 17.04 amd64:
$ systemd-resolve google.com
google.com: resolve call failed: DNSSEC validation failed: signature-expired

Revision history for this message
themusicgod1 (themusicgod1) wrote :

can you ping things that are not domain names but are out on the public internet?
ie ping 8.8.8.8 ?

Revision history for this message
Marzanna (marzanna) wrote :

I can ping DNS server by IP. Host are not reachable if accessed by domain names.

Revision history for this message
Noam Mor (noam-mor) wrote :

Same here. Adding 8.8.8.8 in NetworkManager didn't work. Pinging websites didn't work, but pinging their IP did work. Weirdly, even when ping didn't work, it printed the IP.

As suggested here:

https://askubuntu.com/questions/905543/ubuntu-17-04-weird-dns-issue

I disabled DNSSEC. Now I can access the Internet.

Revision history for this message
ed20900 (ed20900) wrote :

I installed Ubuntu 17.04 as a VirtualBox guest and I have the same problem:
syslog output:
systemd-resolved[947]: DNSSEC validation failed for question . in DNSKEY: missing-key
systemd-resolved[947]: DNSSEC validation failed for question com in DS: missing-key
systemd-resolved[947]: DNSSEC validation failed for question com in DNSKEY: missing-key
systemd-resolved[947]: DNSSEC validation failed for question ubuntu.com in DS: missing-key
systemd-resolved[947]: DNSSEC validation failed for question ubuntu.com in SOA: missing-key
systemd-resolved[947]: DNSSEC validation failed for question apps.ubuntu.com in DS: missing-key
systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in DS: missing-key
systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in SOA: missing-key
systemd-resolved[947]: DNSSEC validation failed for question search.apps.ubuntu.com in A: missing-key

Revision history for this message
dino99 (9d9) wrote :

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

Changed in network-manager (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.