Yes, this is a captive portal situation on up-to-date 17.10. The captive portal popup fails with a DNS error looking for securelogin.arubanetworks.com and then hilarity ensues. Manually editing /etc/resolv.conf to use one of these DNS servers makes it all work. So the problem is systemd-resolved which is the default resolv.conf:
~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search invitados
It's all NM:
~$ cat /etc/netplan/01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Should /etc/resolv.conf be a symlink?
libnss-resolve is not installed.
systemd-resolve --status shows the two local DNS servers, as above.
~$ systemd-resolve --status | cat -
Global
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 7 (wwp0s20f0u6i12)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 4 (wlp4s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 208.67.222.222 208.67.220.220
DNS Domain: invitados
Link 2 (enp0s31f6)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Yes, this is a captive portal situation on up-to-date 17.10. The captive portal popup fails with a DNS error looking for securelogin. arubanetworks. com and then hilarity ensues. Manually editing /etc/resolv.conf to use one of these DNS servers makes it all work. So the problem is systemd-resolved which is the default resolv.conf:
~$ cat /etc/resolv.conf resolved( 8). Do not edit.
# This file is managed by man:systemd-
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53
search invitados
It's all NM:
~$ cat /etc/netplan/ 01-network- manager- all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: NetworkManager
Should /etc/resolv.conf be a symlink?
libnss-resolve is not installed.
systemd-resolve --status shows the two local DNS servers, as above.
~$ systemd-resolve --status | cat -
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
Global
DNSSEC NTA: 10.in-addr.arpa
Link 7 (wwp0s20f0u6i12)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 4 (wlp4s0)
208.67. 220.220
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 208.67.222.222
DNS Domain: invitados
Link 2 (enp0s31f6)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no