#9845 HIGH 10.1.3: Alternative to Create a new wireless network.

[Zarro Boogs per Child]

#9845: Alternative to Create a new wireless network.
------------------------------+---------------------------------------------
           Reporter:  reuben  |       Owner:  erikos                           
               Type:  defect  |      Status:  new                              
           Priority:  high    |   Milestone:  10.1.3                           
          Component:  sugar   |     Version:  Development build as of this date
         Resolution:          |    Keywords:                                   
        Next_action:  review  |    Verified:  0                                
Deployment_affected:          |   Blockedby:                                   
           Blocking:          |  
------------------------------+---------------------------------------------

Comment(by erikos):

 Thanks James for testing!

 Replying to [comment:16 Quozl]:
 > Regarding the test cases provided:
 >
 > > start machine A and connect to the Ad-hoc network 6, start machine B
 without having been connected to an AP before. ... ''machine B should
 autoconnect to the Ad-hoc network 6''
 >
 > Pass.  Additional delay experienced.
 >
 > Machine B showed on the frame device icon palette and the mesh box an
 attempt to join mesh on channel 1 before a successful join of the ad-hoc
 network.  It did autoconnect to ad-hoc network 6, but not before it tried
 to join mesh.

 Did you test with XO-1 and XO-1.5? Please test with XO-1-5 only for now.
 As I said to mikus the GConf setting is not set in the rpms.

 > > start the machine without having connected to an AP before ... ''the
 machine should autoconnect to Ad-hoc network 1''
 >
 > Pass and fail.
 >
 > This worked for machine A (an XO-1.5), with only one AP nearby, but not
 for machine B (an XO-1) in the same circumstance.  Machine B had connected
 to Mesh Network 1.  According to frame device icon palette, iwconfig, and
 ifconfig.  Machine B also showed an additional grey circle icon in frame.
 Machine A showed ad-hoc network 1 was occupied, though this wasn't
 reflected in iwlist scan results for either machine.

 Same here. Please test only with XO-1.5 for now.

-- 
Ticket URL: <http://dev.laptop.org/ticket/9845#comment:18>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system