[Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)
Presumably NetworkManager, I just selected 3 Internet from the connections icon in the top-right corner of the screen (after disabling Wi-Fi from the same place). However, I'm now running Ubuntu 17.10 and systemd-resolve --status is showing the correct DNS servers when connected to 4G. So, this appears to now be fixed, and this report can be closed. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683066 Title: Broken DNS when using Three UK mobile internet (17.04 zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)
** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+attachment/4862776/+files/UdevDb.txt ** Description changed: When connected via 4G to Three/3 (UK), DNS lookups fail (though the internet is otherwise working). The connection receives the correct DNS servers, but as far as I can work out systemd-resolve is unaware of them. Connection info screenshot is attached. DNS lookups time out: $ nslookup www.bbc.co.uk ;; connection timed out; no servers could be reached However they work when manually specifying the DNS server: $ nslookup www.bbc.co.uk 217.171.132.0 Server: 217.171.132.0 Address: 217.171.132.0#53 Non-authoritative answer: www.bbc.co.uk canonical name = www.bbc.net.uk. Name: www.bbc.net.uk Address: 212.58.246.54 Name: www.bbc.net.uk Address: 212.58.244.26 Connections to IP addresses work (though redirect to a Three page at present): $ curl http://212.58.246.54 -v * Rebuilt URL to: http://212.58.246.54/ * Trying 212.58.246.54... * TCP_NODELAY set * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0) > GET / HTTP/1.1 > Host: 212.58.246.54 > User-Agent: curl/7.52.1 > Accept: */* - > + > < HTTP/1.1 302 Moved Temporarily < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html < Content-Type: text/plain; charset=UTF-8 < Content-Length: 0 - < + < * Curl_http_done: called premature == 0 * Connection #0 to host 212.58.246.54 left intact Below is the output of systemd-resolve --status: $ systemd-resolve --status Global - DNS Servers: 8.8.8.8 - 8.8.4.4 - 2001:4860:4860:: - 2001:4860:4860::8844 - DNSSEC NTA: 10.in-addr.arpa - 16.172.in-addr.arpa - 168.192.in-addr.arpa - 17.172.in-addr.arpa - 18.172.in-addr.arpa - 19.172.in-addr.arpa - 20.172.in-addr.arpa - 21.172.in-addr.arpa - 22.172.in-addr.arpa - 23.172.in-addr.arpa - 24.172.in-addr.arpa - 25.172.in-addr.arpa - 26.172.in-addr.arpa - 27.172.in-addr.arpa - 28.172.in-addr.arpa - 29.172.in-addr.arpa - 30.172.in-addr.arpa - 31.172.in-addr.arpa - corp - d.f.ip6.arpa - home - internal - intranet - lan - local - private - test + DNS Servers: 8.8.8.8 + 8.8.4.4 + 2001:4860:4860:: + 2001:4860:4860::8844 + DNSSEC NTA: 10.in-addr.arpa + 16.172.in-addr.arpa + 168.192.in-addr.arpa + 17.172.in-addr.arpa + 18.172.in-addr.arpa + 19.172.in-addr.arpa + 20.172.in-addr.arpa + 21.172.in-addr.arpa + 22.172.in-addr.arpa + 23.172.in-addr.arpa + 24.172.in-addr.arpa + 25.172.in-addr.arpa + 26.172.in-addr.arpa + 27.172.in-addr.arpa + 28.172.in-addr.arpa + 29.172.in-addr.arpa + 30.172.in-addr.arpa + 31.172.in-addr.arpa + corp + d.f.ip6.arpa + home + internal + intranet + lan + local + private + test Link 4 (wlp4s0) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade + DNSSEC supported: yes Link 3 (wwp0s20f0u6i12) - Current Scopes: LLMNR/IPv4 LLMNR/IPv6 -LLMNR setting: yes + Current Scopes: LLMNR/IPv4 LLMNR/IPv6 + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade + DNSSEC supported: yes Link 2 (enp0s31f6) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: allow-downgrade - DNSSEC supported: yes + DNSSEC setting: allow-downgrade +
[Bug 1683066] Re: Broken DNS when using Three UK mobile internet (17.04 zesty)
Update: The ISP redirect has now gone away and the internet now works. However, if the output of systemd-resolve --status is anything to go by systemd-resolve appears to still be using Google DNS instead of my ISP's (which seems utterly bizarre). I would surmise that while the redirect was in place, systemd-resolve was using Google DNS and access to the Google DNS servers was blocked until the SIM had been set up. This basically makes it impossible to set up the type of SIM I had (https://www.three.co.uk/Free_SIM_MBB/Order) on Ubuntu (I had to do that on Windows). That's because the SIM requires registration, which you have to do via mobile internet while using the SIM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683066 Title: Broken DNS when using Three UK mobile internet (17.04 zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1683066] [NEW] Broken DNS when using Three UK mobile internet (17.04 zesty)
Public bug reported: When connected via 4G to Three/3 (UK), DNS lookups fail (though the internet is otherwise working). The connection receives the correct DNS servers, but as far as I can work out systemd-resolve is unaware of them. Connection info screenshot is attached. DNS lookups time out: $ nslookup www.bbc.co.uk ;; connection timed out; no servers could be reached However they work when manually specifying the DNS server: $ nslookup www.bbc.co.uk 217.171.132.0 Server: 217.171.132.0 Address:217.171.132.0#53 Non-authoritative answer: www.bbc.co.uk canonical name = www.bbc.net.uk. Name: www.bbc.net.uk Address: 212.58.246.54 Name: www.bbc.net.uk Address: 212.58.244.26 Connections to IP addresses work (though redirect to a Three page at present): $ curl http://212.58.246.54 -v * Rebuilt URL to: http://212.58.246.54/ * Trying 212.58.246.54... * TCP_NODELAY set * Connected to 212.58.246.54 (212.58.246.54) port 80 (#0) > GET / HTTP/1.1 > Host: 212.58.246.54 > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 302 Moved Temporarily < Location: http://mbbinfo.three.co.uk/payg_mbb_data_usage2.html < Content-Type: text/plain; charset=UTF-8 < Content-Length: 0 < * Curl_http_done: called premature == 0 * Connection #0 to host 212.58.246.54 left intact Below is the output of systemd-resolve --status: $ systemd-resolve --status Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 3 (wwp0s20f0u6i12) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: allow-downgrade DNSSEC supported: yes Note: Everything works fine on Wi-Fi, this problem is only happening on 4G. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sat Apr 15 20:54:33 2017 InstallationDate: Installed on 2017-04-08 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) MachineType: LENOVO 20HDCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=88cb6912-997a-41b4-a0f8-050239177218 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET53W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1QET53W(1.28):bd03/29/2017:svnLENOVO:pn20HDCTO1WW:pvrThinkPadT470:rvnLENOVO:rn20HDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20HDCTO1WW dmi.product.version: ThinkPad T470 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "Connection information screenshot" https://bugs.launchpad.net/bugs/1683066/+attachment/4862764/+files/three-conn-info.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1683066 Title: Broken DNS when using Three UK mobile internet (17.04 zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683066/+subscriptions --
[Bug 1518457] Re: kswapd0 100% CPU usage
I last commented when I was on 15.10, but was just hit by this on 16.04. Again, EC2 t2.micro instance. $ uname -a Linux ip-172-31-45-223 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ top top - 21:32:32 up 6 days, 20 min, 1 user, load average: 1.01, 1.02, 0.96 Tasks: 135 total, 2 running, 133 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us,100.0 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 1014560 total, 426728 free, 215352 used, 372480 buff/cache KiB Swap:0 total,0 free,0 used. 733288 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 30 root 20 0 0 0 0 R 99.7 0.0 44:42.28 kswapd0 5434 ubuntu20 0 40512 3620 3032 R 0.3 0.4 0:00.03 top 1 root 20 0 37796 5880 4008 S 0.0 0.6 0:25.73 systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518457] Re: kswapd0 100% CPU usage
This has also been affecting me on a t2.micro EC2 instance with Ubuntu 15.10, most recently occurred with: 4.2.0-30-generic #36-Ubuntu SMP Fri Feb 26 00:58:07 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux For me it often triggers when installing updates (probably kernel ones in particular). Otherwise the server is not doing much so probably not much of a surprise it doesn't trigger on other occasions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518457 Title: kswapd0 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
