[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
I can ping DNS server by IP. Host are not reachable if accessed by domain names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
can you ping things that are not domain names but are out on the public internet? ie ping 8.8.8.8 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
In Xubuntu 17.04 amd64: $ systemd-resolve google.com google.com: resolve call failed: DNSSEC validation failed: signature-expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
Tested todays daily iso (2017-02-02), can't reproduce this bug. ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650927 Title: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1650927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650927] Re: accessing local ethernet is possible, accessing internet is not possible (Ubuntu MATE 17.04, ppc)
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]: [1478201045.0541] device (wlP1p17s0): Activation: successful, device activated. Nov 03 19:24:05 ubuntu-mate NetworkManager[2012]: [1478201045.0019] policy: set 'Carcosa' (wlP1p17s0) as default for IPv4 routing and DNS Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.9885] manager: NetworkManager state is now CONNECTED_GLOBAL Nov 03 19:24:04 ubuntu-mate systemd[1]: Starting Network Manager Script Dispatcher Service... Nov 03 19:24:04 ubuntu-mate dbus[1946]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.9353] manager: NetworkManager state is now CONNECTED_LOCAL Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.9264] device (wlP1p17s0): state change: secondaries -> activated (reason 'none') [90 100 0] Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.9118] device (wlP1p17s0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.8959] device (wlP1p17s0): state change: ip-config -> ip-check (reason 'none') [70 80 0] Nov 03 19:24:04 ubuntu-mate avahi-daemon[2034]: Registering new address record for 192.168.3.2 on wlP1p17s0.IPv4. Nov 03 19:24:04 ubuntu-mate avahi-daemon[2034]: New relevant interface wlP1p17s0.IPv4 for mDNS. Nov 03 19:24:04 ubuntu-mate avahi-daemon[2034]: Joining mDNS multicast group on interface wlP1p17s0.IPv4 with address 192.168.3.2. Nov 03 19:24:04 ubuntu-mate dhclient[4609]: bound to 192.168.3.2 -- renewal in 3536 seconds. Nov 03 19:24:04 ubuntu-mate NetworkManager[2012]: [1478201044.8428] dhcp4 (wlP1p17s0): state changed unknown -> bound Nov 03 19:24:04
