#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 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.

 > 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.

 All the other test cases passed.  Well done.

 ----

 Regarding the design ... I disagree with Mikus, I think that the XO-1
 should connect to the existing ad-hoc of two systems rather than the
 existing mesh of five XO-1 systems.  This is so that in a rolling upgrade
 scenario, the new way of working is better supported than the old.

 ----

 Replying to [comment:15 mikus]:
 > The channel-1 icon in the XO-1.5's Neighborhood remained colored, rather
 than reverting to white (as the channel-6 and channel-11 icons were).

 The test case says to allow 10-15 minutes after the ad-hoc signal has
 departed the environment.  Did you allow that delay to occur?

 As far as the design goes, I'd like the delay to be more like one minute
 than 10-15 minutes, but I don't believe this would block acceptance of the
 feature.

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