Closed
Bug 1047294
Opened 12 years ago
Closed 12 years ago
[Wifi] Device keeps trying to connect to WLAN more than 30 times when connect to WPA-EAP TTLS/PEAP network using wrong server certificate
Categories
(Firefox OS Graveyard :: Wifi, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2.1 S2 (15aug)
People
(Reporter: gchang, Assigned: chucklee)
References
Details
(Whiteboard: [2.0-flame-test-run-3][p=3])
Attachments
(2 files, 1 obsolete file)
|
154.94 KB,
text/x-log
|
Details | |
|
1.80 KB,
patch
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #1020212 +++
### Steps:
1. Tap "Manage certificates" > "Import certificate"
2. Select a wrong certificate from sd card
3. Navigate to Settings > Wi-Fi page
4. Choose the network supporting WPA-EAP TTLS/PEAP
5. Select "TTLS" or "PEAP" in EAP method
6. Type username and password
7. Select the wrong certificate imported in step 2
8. Tap "OK" button
### Expected:
Device should not keep trying to connect to WPA-EAP TTLS network
### Actual:
Device keep trying to connect to the wireless network
### Reproduce rate
always
### Version:
Device flame
Gaia 73fe34db6caad49bf732d7be3ecfca28b482d74f
Gecko https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/2631725af366
BuildID 20140731160212
Version 32.0
| Reporter | ||
Comment 1•12 years ago
|
||
Updated•12 years ago
|
Whiteboard: [p=13] → [2.0-flame-test-run-3]
Comment 2•12 years ago
|
||
Gerry - Do you think this is a blocker for 2.0 or not?
Flags: needinfo?(gchang)
| Reporter | ||
Comment 3•12 years ago
|
||
Hi Jason,
No, I don't think this is a blocker because the functionality is not broken and it will end trying to connect to the WLAN (after more than 30~50 failures).
Flags: needinfo?(gchang)
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → chulee
| Assignee | ||
Comment 4•12 years ago
|
||
wpa_supplicant reports CTRL-EVENT-EAP-TLS-CERT-ERROR in a burst in such condition(I don't know why), and even we command it to disable wifi ever 3 failure events, we can't stop it from retrying right away. But the retry should stop eventually.
While capturing the error on my own, I observe some Javascript Error in WifiWorker.js under this rapid event condition, maybe fix them can decrease the retry number a little.
| Assignee | ||
Comment 5•12 years ago
|
||
Validate ssid string before dequoting, and fix dequoting target.
Test 6 times continuously with retry count of 10, 12, 6, 8, 4, 10.
Attachment #8467629 -
Flags: review?(vchang)
Comment 6•12 years ago
|
||
Comment on attachment 8467629 [details] [diff] [review]
Fix potential Javascript Error.
Review of attachment 8467629 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good.
Attachment #8467629 -
Flags: review?(vchang) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
Add reviewer's name.
Attachment #8467629 -
Attachment is obsolete: true
| Assignee | ||
Updated•12 years ago
|
Attachment #8469162 -
Attachment description: 0001. Fix potential Javascript Error. r=vchang → Fix potential Javascript Error. r=vchang
| Assignee | ||
Comment 8•12 years ago
|
||
| Assignee | ||
Comment 9•12 years ago
|
||
Try looks good.
Keywords: checkin-needed
Whiteboard: [2.0-flame-test-run-3] → [2.0-flame-test-run-3][p=3]
Target Milestone: --- → 2.1 S2 (15aug)
Comment 10•12 years ago
|
||
Keywords: checkin-needed
Comment 11•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 12•12 years ago
|
||
verified @
Gaia c7f8938522a18454809fb6ea0fd3eddef10a73ea
Gecko https://hg.mozilla.org/mozilla-central/rev/9eb591a1a203
BuildID 20140814160206
Version 34.0a1
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•