Closed Bug 855194 Opened 11 years ago Closed 11 years ago

[Buri][WIFI]Other device should display WPS available when set MS's hotspot security is WPA

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P2)

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(blocking-b2g:tef+)

Status:
RESOLVED INCOMPLETE
Milestone:
1.0.1 Cert2 (21may)
Project Flags:
blocking-b2g tef+

People

(Reporter: sync-1, Assigned: m1)

Details

AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.19.044
 Firefox os  v1.0.1
 Mozilla build ID: 20130319070203
 
 +++ This bug was initially created as a clone of Bug #427391 +++
 
 Created an attachment (id=371649)
 when security set open,other device search ,it display WPS available
 
 DEFECT DESCRIPTION:
 Other device should display WPS available when set MS's hotspot security is WPA
 REPRODUCING PROCEDURES:
 1.data connection is on
 2.Setting->Internet sharing->Hotspot settings->Set Security:WPA(TKIP)
 3.use other device to serch MS's SSID,find it does not display WPS available->KO1
 4.when I set Security is Open or WPA2(AES),use other device serach MS's SSID,it display WPS available
 EXPECTED BEHAVIOUR:
 1.It shuould display WPS available
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 
 REPRODUCING RATE:5/5
 
 For FT PR, Please list reference mobile's behavior:
 
 ++++++++++ end of initial bug #427391 description ++++++++++
 
 
 
 CONTACT INFO (Name,Phone number):
 
 DEFECT DESCRIPTION:
 
 REPRODUCING PROCEDURES:
 
 EXPECTED BEHAVIOUR:
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 
 REPRODUCING RATE:
 
 For FT PR, Please list reference mobile's behavior:
Do we need to support WPS when enabling wifi hotspot ? Currently, we don't support this feature. We may need to check hostapd to see if we can disable wps capability in both cases.
(In reply to Vincent Chang[:vchang] from comment #1)
> Do we need to support WPS when enabling wifi hotspot ? Currently, we don't
> support this feature. We may need to check hostapd to see if we can disable
> wps capability in both cases.

It does not mean that.It means when enabling wifi hotspot use firefox OS phone,the other device like android phone display wrong info. For Example when I set Security is Open or WPA2(AES),other device (android OS) display 'WPS available' or 'Secured whis WPA2(WPS available)'. But when I set Secyrity is WPA(TKIP),other device (android OS) display 'other device (android OS) display 'Secured whis WPA',it does not display 'WPS available'
(In reply to rayren2012 from comment #2)
> (In reply to Vincent Chang[:vchang] from comment #1)
> > Do we need to support WPS when enabling wifi hotspot ? Currently, we don't
> > support this feature. We may need to check hostapd to see if we can disable
> > wps capability in both cases.
> 
> It does not mean that.It means when enabling wifi hotspot use firefox OS
> phone,the other device like android phone display wrong info. For Example
> when I set Security is Open or WPA2(AES),other device (android OS) display
> 'WPS available' or 'Secured whis WPA2(WPS available)'. But when I set
> Secyrity is WPA(TKIP),other device (android OS) display 'other device
> (android OS) display 'Secured whis WPA',it does not display 'WPS available'

That's why we have to check the hostapd to see why we have WPS tag in the beacon.
Hi Vincent
do you have any news?
Dear Mozilla team,
 
 Any update?
The WPS available flag is controlled by hostapd, and hostapd is created by netd. Both modules are coming from codeaurora's ics_strawberry_v1 branch.

Michael, can you help to check this ? Any comment is very appreciated.  

I dumped the hostapd.conf from buri device below. The wps_state is not set and should be the default value 0, which indicate that wps is disabled.    
ap_scan=2
network={
mode=2
ssid="Firefoxqqqqqqi"
frequency=2412
key_mgmt=NONE
}
Flags: needinfo?(mvines)
any updates?
blocking-b2g: --- → tef?
Flags: needinfo?(anshulj)
Whiteboard: [tef-triage]
Flags: needinfo?(anshulj)
I'm currently not able to reproduce this issue on either the Buri or QRD at the tip of v1.0.1.

Does it still reproduce for sync-1?
Flags: needinfo?(mvines)
Flags: needinfo?(sync-1)
ni? Cheng-an for question in comment 8
Flags: needinfo?(chengan.xiong)
Dear：
  Phone supoort WPS,so WPS is 1.0 or 2.0?
 thanks
Flags: needinfo?(sync-1)
Micheal, looks like it does repro for sync-1 --- go ahead with blocking?
Flags: needinfo?(mvines)
I don't have an opinion on blocking or not.  If QC support is requested here please file an SR.  Thanks!
Flags: needinfo?(mvines)
I cannot reproduce it either, can the reporter check if this still happening, and if so, exact steps to reproduce?
Flags: needinfo?(sync-1)
(In reply to comment #13)
 > Comment from Mozilla:I cannot reproduce it either, can the reporter check if
 > this still happening, and if so, exact steps to reproduce?
 
 Dear Mozilla team,
    the exact steps:
     (1)turn on data connection
     (2)Settings->Internet sharing->Hotspot settings->Security:WPA(TKIP),then click "OK"->turn on Wi-Fi hotspot
     (3)Use other phone to search it,it not display "WPS available",it display"Secured with WPA"-->KO
     (4)when set the Security is "Open" or "WPA2(AES)",other phone search it,it  dispaly "WPS available" 
     I consult some documents now,it may be not a problem.WPS have WPS 1.0 and WPS 2.0;
     WPS 1.0 support open ,WPA and WPA2
     WPS 2.0 support open and WPA2
     please tell me WPS is 1.0 or 2.0 in FFOS?
 thanks
Flags: needinfo?(sync-1)
Flags: needinfo?(chengan.xiong)
Vincent - can you answer the question in comment 14?  It looks like if we're supporting WPS 2.0 we do not need to block on this bug as we are meeting spec.
Flags: needinfo?(vchang)
wifi-hotspot(Access point mode) 
=> don't support WPS. 

wifi(station mode) 
=> dependent on the version of wpa_supplicant, should support WPS 2.0.
Flags: needinfo?(vchang)
(In reply to Vincent Chang[:vchang] from comment #16)
> wifi-hotspot(Access point mode) 
> => don't support WPS. 
> 
> wifi(station mode) 
> => dependent on the version of wpa_supplicant, should support WPS 2.0.

Hi Vincent，

I use wifi-hostpot and set the Security is "Open" or "WPA2(AES)", other phone(android) search it,it  dispaly "WPS available" . But based on your comment, it is not support WPS. Is it a bug? If so,when did you check it?
> I use wifi-hostpot and set the Security is "Open" or "WPA2(AES)", other
> phone(android) search it,it  dispaly "WPS available" . But based on your
> comment, it is not support WPS. Is it a bug? If so,when did you check it?

Please check comment 6.
Hi Michael and Daniel,

 the exact steps:
     (1)turn on data connection
     (2)Settings->Internet sharing->Hotspot settings->Security:WPA(TKIP),then click "OK"->turn on Wi-Fi hotspot
     (3)Use other phone(android) to search it,it display"Secured with WPA"
     (4)when set the Security is "Open" or "WPA2(AES)",other phone(android) search it,it  dispaly "WPS available" 

 Based on comment 16, it don't support WPS. But when set security "OPEN" or "WPA2(AES)" ,it display "WPS available". Please check why it dispalyed?
Michael, assigning to your team to look into the potential display bug here.  If you disagree with the str in comment 19 being a bug, please go ahead and minus this bug - we've circled this one too much.
Assignee: nobody → mvines
blocking-b2g: tef? → tef+
Note that if we don't have a call on this by 5/10 this will be dropped from blocking.
Whiteboard: [tef-triage]
Whiteboard: [status: awaiting mvines' call]
This doesn't seem like a big deal to me, just my 2 cents.  Comment 12 still applies please.
Whiteboard: [status: awaiting mvines' call]
set milestone to partner bug
Target Milestone: --- → 1.0.1 Cert2 (28may)
do you already have an SR for mvines to support you? Thanks
Flags: needinfo?(mei.kong)
Case ID: 01184519
Flags: needinfo?(mei.kong)
the cause is supplicant detect wps IE exist. so show wps_available.
it means hot-spot's beacon or probe response frame contain WPS IE. 
if we disable WPS feature in hot-spot side, this issue should be fixed.
Resolving this bug as the issue is being worked via SR, so there's no further action here at this time.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.