816698 - [wifi] wifi does not automatically reconnect to a secure network

Status: VERIFIED WORKSFORME

(Core :: DOM: Device Interfaces, defect, P2)

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

## Environment :
Unagi phone, build 2012/11/29
  
## Repro :
1. connect Mozilla G or some other secure network
2. let the phone sleep
3. wake the phone

## Expected :
1. wifi should automatically connect agian

## Actual :
1. wifi scans and fails to reconnect

## Note :
11-29 13:12:14.831: W/wpa_supplicant(377): wlan0: EAP-MSCHAPV2: failure message: 'Authentication Failure' (retry allowed, error 691)

Comment 1

[Vincent Chang[:vchang][changyihsin]]

I found the same log while trying to connect to "Mozilla-G" with incorrect username. Here is my log, 
W/wpa_supplicant(  820): wlan0: EAP-MSCHAPV2: failure message: 'Authentication Failure' (retry allowed, error 691)

Can you help to double check if the username and password are correct ? 
You can find them in /data/misc/wifi/wpa_supplicant.conf. 

network={
	ssid="Mozilla-G"
	key_mgmt=WPA-EAP
	identity="vchang@mozilla. com" <= here is typo, one extra space 
	password="xxxxxxxxxxxx"
	priority=1
}

Comment 2

[Dylan Oliver [:doliver]]

blocking+

This has only been observed/reproducible on the Mozilla-G network so far, might be related to the specific config we use?  Need investigation.

Comment 3

[Chris Lee [:clee]]

Which wifi security versions does this impact?  Is it only EAP-MSCHAPV2?

Comment 4

[Dylan Oliver [:doliver]]

qawanted to try on different security configs

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I don't have the same type unfortunately.  QAwanted also not just to do security but various connection type testing.  ie rebooting phone versus timeout is different code pathing I believe.

network={
	ssid="Mozilla-G"
	key_mgmt=WPA-EAP
	identity="[e-mail]"
	password="xxxxxxxxxxxxx"
}

Comment 6

[Vincent Chang[:vchang][changyihsin]]

(In reply to Naoki Hirata :nhirata from comment #5)
> I don't have the same type unfortunately.  QAwanted also not just to do
> security but various connection type testing.  ie rebooting phone versus
> timeout is different code pathing I believe.
> 
> network={
> 	ssid="Mozilla-G"
> 	key_mgmt=WPA-EAP
> 	identity="[e-mail]"
> 	password="xxxxxxxxxxxxx"
> }
The difference is that we have a clean wifi driver when doing the reboot. Not sure if it is related to the driver. I also connect to "Mozilla-G" network, but I am not be able to reproduce this bug in Taipei office. Any difference between these two APs ? Can it be reproduced all the time when trying to connect with "Mozilla-G" network ?

Comment 7

[David Scravaglieri [:scravag]]

gecko-beta: 1e56f66d7ee9
gaia: ea68f5ece44baeb6806be78e0ae33c1ea6d29445

Works fine with WPA-PSK
Doesn't work with WPA-EAP (EAP-MSCHAPV2)

I validate the Naoki scenario and results.

Comment 8

[Joe Drew (not getting mail)]

My WEP network (802.11g) is also affected by this.

Comment 9

[Andrew Overholt [:overholt]]

Blake, can you help sort out the situation here?  Is WPA-EAP the thing we're not supporting?  Joe's issue with WEP in comment #8 concerned us during triage.

Comment 10

[Alex Keybl [:akeybl]]

Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.

Comment 11

[Dietrich Ayala (:dietrich)]

No update from assignee in 10 days. Blake, any update?

I'm not seeing this locally - reconnect to my authenticated networks on recent Unagi builds.

Comment 12

[Joe Drew (not getting mail)]

Since I wiped my Unagi phone and re-flashed with the beta build, my phone now connects automatically to my WEP network.

Comment 13

[Andrew Overholt [:overholt]]

(In reply to Joe Drew (:JOEDREW! \o/) from comment #12)
> Since I wiped my Unagi phone and re-flashed with the beta build, my phone
> now connects automatically to my WEP network.

Thanks for the update, Joe.

If others see this behaviour, please re-open.