search

ubports / ubuntu-touch

Ubuntu Touch's issue inbox is now migrated to GitLab.
https://gitlab.com/ubports/ubuntu-touch
1.29k stars 110 forks source link

[16.04] Wifi - not working - WPA Enterprise/PEAP/MSCHAPv2 #859

Open ImmanuelSamuel opened 6 years ago

ImmanuelSamuel commented 6 years ago

[BUG]

Steps to reproduce

This is a typical wifi configuration for enterprise customers.

Expected behavior

Wifi connection

Actual behavior

No wifi

Logfiles and additional information

cat /var/log/syslog

Sep 3 13:18:31 ubuntu-phablet repowerd[853]: DefaultStateMachine: handle_user_activity_extending_power_state Sep 3 13:18:32 ubuntu-phablet repowerd[853]: DefaultStateMachine: handle_user_activity_extending_power_state Sep 3 13:18:33 ubuntu-phablet wpa_supplicant[775]: wlan0: Failed to initiate sched scan Sep 3 13:18:33 ubuntu-phablet kernel: [ 483.907792] [rmnet7] error: rmnet_ioct called for unsupported cmd[35143] Sep 3 13:18:33 ubuntu-phablet kernel: [ 491.412089] wlan: [775:E :HDD] __wlan_hdd_cfg80211_sched_scan_start: Network input is not correct 0 Max Network supported is 16 Sep 3 13:18:34 ubuntu-phablet repowerd[853]: DefaultStateMachine: handle_user_activity_extending_power_state Sep 3 13:18:34 ubuntu-phablet wpa_supplicant[775]: wlan0: Failed to initiate sched scan Sep 3 13:18:34 ubuntu-phablet kernel: [ 493.034641] wlan: [775:E :HDD] wlan_hdd_cfg80211_sched_scan_start: Network input is not correct 0 Max Network supported is 16 Sep 3 13:18:35 ubuntu-phablet repowerd[853]: DefaultStateMachine: handle_user_activity_extending_power_state Sep 3 13:18:37 ubuntu-phablet repowerd[853]: message repeated 2 times: [ DefaultStateMachine: handle_user_activity_extending_power_state] Sep 3 13:18:59 ubuntu-phablet wpa_supplicant[775]: wlan0: Failed to initiate sched scan Sep 3 13:18:59 ubuntu-phablet kernel: [ 518.286076] wlan: [775:E :HDD] wlan_hdd_cfg80211_sched_scan_start: Network input is not correct 0 Max Network supported is 16

Flohack74 commented 6 years ago

Hi, the log file unfortunately tells me nothing. What I can say though is that I use a WPA2-Enterprise/PEAP/MSCHAPv2 without issues here on the OPO...

Arc676 commented 6 years ago

I don't have my device with me right now, but I'm 80% sure I have the same configuration working on flo (Nexus 7, wifi) running 15.04/stable.

ImmanuelSamuel commented 6 years ago

Well I am still having issues with this unfortunately. I can connect to other wifi networks that do not have this configuration. I was wondering if any logs can show what is going wrong?

cyberpunkedu commented 6 years ago

I have been able to connect to Enterprise networks. Check a few things (not necessarily at the same time):

  1. Make sure that the user name is in the "identity" box. For some reason there is a box that says anonymous identity that allows text input (??)
  2. Try using MSCHAP instead of MSCHAPv2 (even though it should be v2!)
  3. For me it took longer than expected for the device to connect to the network, so waiting a bit... or check with the network admin to make sure that the connection is working and allows more than one device to connect with your id at the same time.
frgigr commented 6 years ago

Hi, I was also able to connect to Enterprise networks (eduroam, to be precise)..Below you can find the settings I used as well as the device used:

  1. Security WPA and WPA2 Enterprise
  2. Authentication PEAP
  3. PEAP version Automatic
  4. Inner Authentication MSCHAPv2
  5. Anonymous Identity left blank
  6. Then Your Username and Password and tick the box Remember Password, otherwise I got the message Incorrect username or password

Hope this helps!

YougoCodes commented 6 years ago

Device: Fairphone 2 OS: Ubuntu Touch 16.04/rc (2018-W40)

connection to WPA2-Enterprise works with the following settings

  1. Security WPA and WPA2 Enterprise
  2. Authentication PEAP
  3. PEAP version Automatic
  4. Inner Authentication MSCHAPv2
  5. Anonymous Identity left blank
  6. Then Your Username and Password and tick the box Remember Password, otherwise I got the message Incorrect username or password

however finding those settings isn't intuitive at all. while this particular setup is fairly common and a good one to try first, the only method of finding the correct settings is to try them all, or find an admin who can tell you.

so: expected behavior: device sniffs out the correct settings (or tries them all automatically without bothering the user) and connects without fuss like all the common mobile devices/os'ses do

experienced behavior the device detects the network to be "WPA2 personal", which will fail, and presents a myriad of options for the user to figure out for themselves.

at the request of @UniversalSuperBox below some pastebins:

/var/log/syslog dmesg output

ImmanuelSamuel commented 6 years ago

I have tried many combinations and some of which were according to the previous posts still no connections. Can maybe try again after a few updates to see if it still persists.

luk-s commented 6 years ago

Device: Fairphone 2 OS: Ubuntu Touch 15.04 (r3)

Trying to connect to a WPA2-Enterprise that has the following official config recommendations: Security Specification: WPA2-Enterprise Encryption Specification: AES Network Authentication Protocol: PEAP Authentication Protocol: EAP-MSCHAP v2 Certificate: None/Inactive

There are also devices that are able to connect to this network via PEAP with GTC so in the following I tried to connect using those two combinations and using the following settings in the "system settings" app:

First try: the official recommendations

  1. Security: WPA & WPA2 Enterprise
  2. Authentication: PEAP
  3. Inner authentication: MSCHAPv2
  4. CA certificate: None
  5. PEAP version: Automatic
  6. Anonymous Identity: left blank
  7. Username and Password

Second try: Using PEAP with GTC

  1. Security: WPA & WPA2 Enterprise
  2. Authentication: PEAP
  3. Inner authentication: GTC
  4. CA certificate: None
  5. PEAP version: Automatic
  6. Anonymous Identity: left blank
  7. Username and Password

expected behavior in both tries: connection to the network gets successfully established

experienced behavior in both tries: Short loading, then I am back at the "Connect to Wi-Fi" mask with all my settings and information still the way I entered them. No connection was established, no error message was shown.

Some logs that may help: dmesg output /var/log/syslog

cyberpunkedu commented 6 years ago

I found that checking "Remember password" seems to be an important step.

Also, the inner authentication seems to have a few issues:

UniversalSuperBox commented 5 years ago

It should be noted that there are lots of options on this screen because an Enterprise network can have lots of different authentication settings! When in doubt, ask your IT administrator what settings to use for your Wi-Fi network.

This thread doesn't seem to have found any pattern to the issue yet. @luk-s, I appreciate the log but it looks like it has been truncated at some point and I'm not able to find exactly where the issue occurs.

It is best if logs are taken right after you try to perform the steps where the problem occurs... otherwise I'm lost in a sea of debugging messages. :(