[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
The fix that worked for me is to add the libnss-resolve package. This changes the /etc/nsswitch.conf file to actually attempt the dns lookup after the other conditions have started the UDB fallback mode. Bug 1727237 had a comment requesting if libnss-resolve were installed, answered "no", but no further suggestions regarding the package. The package changes the hosts line in the nsswitch.conf to: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns myhostname -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
We are using lxc Ubuntu 18.04 on proxmox -5.3-7. Network configuration obtain through DHCP. We have desactivate /etc/resolv.conf modification over proxmox to get DHCP DNS use: touch .pve-ignore.resolv.conf Everything line in /etc/resolv.conf is comment: # cat /etc/resolv.conf # --- BEGIN PVE --- #search digicom.ca #nameserver 8.8.8.8 # --- END PVE --- Network status shown DNS entry is OK: #networkctl status ●State: routable Address: 172.16.8.23 on eth0 fe80::a0c5:bbff:fe4f:bc on eth0 Gateway: 172.16.8.1 (ICANN, IANA Department) on eth0 DNS: 104.192.16.1 NTP: 172.16.8.3 104.192.20.4 66.70.172.17 systemd-resolve works fine: #systemd-resolve go.com go.com: 23.236.60.174 -- Information acquired via protocol DNS in 1.3ms. -- Data is authenticated: no But resolve name using ping command or host failed: # ping go.com ping: go.com: Temporary failure in name resolution # host go.com ;; connection timed out; no servers could be reached The work around is to manually create a link to the systemd-resolve conf file: mv /etc/resolv.conf /etc/resolv.conf.orig ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Yes - Catch a flight to the US and go to a starbucks :). Perhaps you can use the Starbucks approach I documented here: https://askubuntu.com/questions/1023429/cant-connect-to-google-starbucks-wifi-on-ubuntu-17-10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
You may think you fixed it but I'm sitting in a hotel in The Netherlands with a connected phone and tablet but not the laptop. Grrr! I have 18.04 up to date yesterday. Wifi says it is connected but hotel logon page won't appear. Is there a usable workaround? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
This bug was fixed in the package systemd - 239-7ubuntu4 --- systemd (239-7ubuntu4) cosmic; urgency=medium * Workaround broken meson copying symlinked data files, as dangling symlinks. -- Dimitri John Ledkov Wed, 22 Aug 2018 14:11:35 +0100 ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Hi, for me it seems to work with latest bionic as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
This bug was fixed in the package systemd - 237-3ubuntu10.2 --- systemd (237-3ubuntu10.2) bionic; urgency=medium * logind: backport v238/v239 fixes for handling DRM devices. These changes introduce all the fixes that correct handling of open fd's related to the DRM devices, as used by for example NVIDIA GPUs. This backport includes some refactoring, corrections, and comment updates. This to insure that correct history is preserved, code comments match reality, and to ease backporting logind fixes in the future SRUs. (LP: #1777099) * Disable dh_installinit generation of tmpfiles for the systemd package. Replace with a manual safe call to systemd-tmpfiles which will process any updates to the tmpfiles shipped by systemd package, taking into account any overrides shipped by other packages, sysadmin, or specified in the runtime directories. (LP: #1748147) systemd (237-3ubuntu10.1) bionic; urgency=medium [ Dimitri John Ledkov ] * hwdb: Fix wlan/rfkill keycode on Dell systems. (LP: #1762385) * Cherrypick upstream fix for corrected detection of Virtualbox & Xen. (LP: #1768104) * Further improve captive portal workarounds. Retry any NXDOMAIN results with lower feature levels, instead of just those with 'secure' in the domain name. (LP: #1766969) [ Michael Biebl ] * Add dependencies of libsystemd-shared to Pre-Depends. This is necessary so systemctl is functional at all times during a dist-upgrade. (Closes: #897986) (LP: #1771791) [ Mario Limonciello ] * Fix hibernate disk offsets. Configure resume offset via sysfs, to enable resume from a swapfile. (LP: #1760106) -- Dimitri John Ledkov Fri, 22 Jun 2018 13:55:09 +0100 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
237-3ubuntu10.2 fixed the issue for me in Bionic. With this version installed I was able to successfully log into the wifi on the train in the Netherlands. Previously I could not load the accept page. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Hello Pete, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Bionic) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Obviously I didn't just jump in and release a fix. I accidentally updated the status and can't set it back. Sorry folks. I didn't mean to get anyone excited about the fix being out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Correction: I did not see the .1 in your version number. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
@Tom: Than it's not the same issue. As this is the version the bug was reported with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
I confirm that 237-3ubuntu10.1 works also -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
I confirm that this fixes the problem for the newly rolled out Starbucks aruba hotspots. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Using 237-3ubuntu10.1, with 8.8.8.8 as DNS server, the resolutions of nonexistant.ubuntu.com and secure.ubuntu.com both are retried with following messages in the journal: systemd-resolved[1434]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. With 237-3ubuntu10, a similar message only appeared for "secure.ubuntu.com" NXDOMAIN query, but not for the nonexistant.ubuntu.com. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Hi, I'd love to help but i won't be in the affected hotel anytime soon. So i hope some of the others could test. Best regards, Pete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Hello Pete, or anyone else affected, Accepted systemd into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Description changed: + [Impact] + + * More captive portals have been discovered that do not handle DNS requests with D0 set. + * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. + + [Test Case] + + * systemd-resolved something-nonexistant.ubuntu.com + * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. + * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches + + [Regression Potential] + + * Legitimate NXDOMAIN queries will now take longer, as they will be + retried multiple times with different features sets until an answer is + found. At that point the query will be cached and will return quickly. + This is needed to work-around bad captive portals that do not support + dns queries with D0. Post-captive portal, the feature level can usually + be cranked back up and it does after a grace period. + + [Other Info] + + * Original bug report + I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working.
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Changed in: systemd (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Committed Bug description: I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: Confirmed ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Artful: New Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Confirmed Bug description: I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
This seems to affect many public Wifi Hotspots. A very common example is the new setup by Starbucks/Google (usually seen as **Google Starbucks Wifi**) in the US by (Tech behind it is https://globalreachtech.com/ with their http://odyssys.net/). Under Ubuntu 16.04, Windows, Android, Mac OS, or iPhone, a WiFi guest user can connect without problem. However, since upgrading to Ubuntu 18.04, I've encountered this in at least three separate Starbucks stores in Southern California. ## WORKAROUND ## An easier workaround, with fewer system modifications than the original bug report is to use `ip route` to determine the IP address of the host router, then add the hostname with that adress to `/etc/hosts` Step by step details can be found here: https://askubuntu.com/a/1027605/139249 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Confirmed Bug description: I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Summary changed: - DNS cannot be resolved in Hotel Hotspot + DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Confirmed Bug description: I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
