[mako] Cannot connect to a secure, shared "ap" hotspot

Bug #1434591 reported by Jonas G. Drange
92
This bug affects 16 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

$ system-image-cli -i
current build number: 138
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-03-17 15:04:46
version version: 138
version ubuntu: 20150317.1
version device: 20150210
version custom: 20150317.1

I have tried most types of security, but the spec [2] says for maximum compatibility, most of the options should be left blank. Blank settings failed on both a and bg bands.

How to reproduce:
1. Create a secure hotspot (I am using this [1] script)
2. Confirm that the hotspot is active and appears secured for other devices

What happens:
Connecting to it fails.

What should have happened:
Connecting to it should not fail.

Excerpt from syslog
http://pastebin.ubuntu.com/10627959/

Insecure hotspots should work using this [3] script.

[1] http://pastebin.ubuntu.com/10683465/
[2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
[3] http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

Tags: connectivity
summary: - [mako] Cannot connecto to a secure, shared "ap" hotspot
+ [mako] Cannot connect to to a secure, shared "ap" hotspot
summary: - [mako] Cannot connect to to a secure, shared "ap" hotspot
+ [mako] Cannot connect to a secure, shared "ap" hotspot
Revision history for this message
Tony Espy (awe) wrote :

@Jonas

There's really not enough information in your bug report for us to reproduce it.

Can you please add your device and image ( RTM? vivid-devel?, # ) details?

What device are you using to create a hotspot? What type of security did you specify? What band of WiFi was used ( 2.4? 5? )?

Changed in network-manager (Ubuntu):
status: New → Incomplete
tags: added: connectivity
Changed in network-manager (Ubuntu):
assignee: nobody → Jonas G. Drange (jonas-drange)
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

@Tony, I have updated the bug with the details you asked for.

description: updated
Changed in network-manager (Ubuntu):
status: Incomplete → New
assignee: Jonas G. Drange (jonas-drange) → nobody
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Also, the [mako] was there from the start. Could mako mean anything else than Nexus 4? In that case, do you need a serial number/production date?

description: updated
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Zoltan tested this and saw this syslog: http://paste.ubuntu.com/11928531/

Changed in network-manager (Ubuntu):
status: New → Confirmed
description: updated
Revision history for this message
alexoverton (alexjoverton) wrote :

Confirm the same. Nexus 4, Stable. Used existing default config on new install.

Revision history for this message
Tony Espy (awe) wrote :

First, hotspot was *not* supposed to have been enabled for mako in OTA6 due to this bug. See bug #1487157.

Re-verified using rc-proposed / #228 ):

A hotspot can be created/started, it's not usable. It can be seen by other devices ( iPhone, Nexus5 ), but neither the device aren't able to properly authenticate to the hotspot:

I also see the following kernel and wpa_supplicant errors on mako when a client attempts to associate.

15:18:19 kernel: [ 1010.424629] wlan: [1484:E :PE ] limProcessAssocReqFrame: 654: AP supports RSN enabled authentication
15:18:22 wpa_supplicant[1945]: handle_probe_req: send failed
15:18:23 wpa_supplicant[1945]: WPA: wpa_sm_step() called recursively
15:18:23 kernel: [ 1014.448283] wlan: [1945:E :HDD] hdd_softap_sta_deauth:(c1117f20, false)

Revision history for this message
Nicolas DERIVE (kalon33) wrote :

@awe : sure it was not supposed to have been enabled and it will be fixed in the next OTA apparently. But where's the problem preventing it from working? Is it planned to fix this? Hotspot functionality is pretty useful and was requested for a long time (it is available on the same hardware in Android too)...

Revision history for this message
André Gregor-Herrmann (andre-herrmann) wrote :

I'm facing the same issue with my nexus 4 which I bought for getting Ubuntu Touch working on this device. Due Hotspot is an essential feature for me I former thought of switching to an Android based Image despite I really like the way Ubuntu-Touch works. Additionally I'm now used to its Gesture-Based interface. Then I heard that Hotspot is coming via OTA-6 and I rather waited, instead of newly flashing the device. Too bad that is still not working on my device then.

If this feature will be a "won't fix for mako", I see no other Chance to regret the further Usage of Ubuntu Touch, which would make me really sad but is then without any alternative for me :-(

Revision history for this message
Sven Hartrumpf (hartrumpf) wrote :

André, I think you are not the only one disappointed ...

But there was a (wired) tethering solution, that I confirmed 2 months ago (haven't tried on newer OTA versions):
https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1427697 more specifically:
https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1427697/comments/5

Has anyone succeeded with this work-around on current OTA versions?
If so, it would be easy to polish this work-around with some scripts or similar and put the resulting description at some more prominent place (where?).

Revision history for this message
Sven Hartrumpf (hartrumpf) wrote :

I have successfully repeated the fix for the current OTA version
and recorded my experience in a new comment:

https://bugs.launchpad.net/ubuntu/+source/dbus-property-service/+bug/1427697/comments/8

Wired tethering still works for Nexus 4!

Revision history for this message
tschoie (tschoie) wrote :

The following is slightly off-topic, but I'm not sure if it justifies a separate bug report (I'm happy to create one if desired) and people here might be able to point me in the right direction:
I temporarily activated the hotspot feature in OTA-6 when it wasn't supposed to land, subsequently realizing that it doesn't work. Meanwhile the hotspot menu entry has been hidden from system settings as per https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1487157, but there is still a hotspot toggle in the network indicator. I was waiting for one of the later OTAs to get rid of it, but that didn't happen so far - I'm on OTA-9 now.
Is there currently any way to (manually) remove network indicator's hotspot toggle on mako?

Revision history for this message
Jonas G. Drange (jonas-drange) wrote : Re: [Bug 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

On 28 January 2016 at 20:37, tschoie <email address hidden> wrote:

> Is there currently any way to (manually) remove network indicator's
> hotspot toggle on mako?

​You should be able to remove it like this:

    $ sudo rm /etc/NetworkManager/system-connections/<Ubuntu> && sudo reboot

Revision history for this message
tschoie (tschoie) wrote :

That worked - thanks a lot, Jonas!

Revision history for this message
Jose' Belmar (swizztek-software) wrote :

What's the latest on this issue? When i flashed touch onto my nexus 4 i saw the hotspot menu item for the first boot, but afterward it disappeared. So does this mean that the hotspot bug will never be fixed for Nexus 4?
I have one slightlty off-topic question:
Is bluetooth file sharing also missing for similar reasons?

Revision history for this message
Fice (fice) wrote :

Wi-fi hotspot works on mako with the current build of LineageOS 14.1 (the successor of CyanogenMod). Will it help to port the kernel from LineageOS?

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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