Ubuntu can't log into starbucks WIFI

Bug #1767900 reported by Ole
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Summarized the problem and the solution here. Apparently all other OSs can authenticate, hence it must be an Ubuntu issue:

https://askubuntu.com/questions/1023429/cant-connect-to-google-starbucks-wifi-on-ubuntu-17-10/1029893#1029893

Revision history for this message
Sebastien Bacher (seb128) wrote :

The issue looks like bug #1727237 which has been fixed in the newest Ubuntu version

Changed in network-manager (Ubuntu):
importance: Undecided → High
Revision history for this message
Ole (ole-ersoy) wrote :

Do you know if there is a regression coming out for 17.10?

Revision history for this message
mike stewart (mdrmike) wrote :

@seb128 I'm in a Starbucks now. #1727237 does not fix my issue.

This seems to be a duplicate of open bug: #1766969 ( https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969 ), which forked from #1727237

**WORKAROUND:**

1. At Starbucks, connect to Google Starbucks WiFi.
2. Jump into a browser to have it identify a "server not found", need the name of the server in the browser address. (Example: Browser hangs on `https://aruba.odyssys.net`)
3. Open terminal and run `ip route` to determine ROUTER.IP (example: `ip route` returns `default via 172.31.98.1`)
4. Lookup the server IP address from local router by running `dig @ROUTER.IP server.not.found` (example: `dig @172.31.98.1 aruba.odyssys.net` returns `;; ANSWER SECTION:
aruba.odyssys.net. 0 IN A 172.31.98.1`)
5. Add IP address to /etc/hosts (Example: `sudo nano /etc/hosts` add the line: `172.31.98.1 aruba.odyssys.net`)
6. Add nameservers to /etc/resolv.conf (Example: `sudo nano /etc/resolv.conf` add lines above existing nameserver `nameserver 172.31.98.1` and `nameserver 8.8.8.8`)

Try again to connect (and don't reboot before connecting).

**Notes:**
After reviewing the output as I was sharing I realized
Step 4 might be totally unnecessary.
Step 5 is a permanent change that likely will affect your ability to connect at other Starbucks.
Step 6 is temporary and systemd will overwrite the file at reboot, possibly sooner.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

This is an issue with Fedora, Kali and the other latest or newest distributions as well. I tried and older distribution of Ubuntu, Fedora, and Kali and they connect to the Starbucks Wifi just fine. I am currently using the fedora 26 and there is no problem connecting. It is not the way the Starbucks wifi is implemented. It is the way it is implemented on the newer distributions. Arch linux didn't have any issues connecting to the wifi at Starbucks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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