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

Zarro Boogs per Child bugtracker at laptop.org
Fri Aug 20 15:41:36 EDT 2010

#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 mikus):

 Installed the new rpms in two (customized) os851 systems - an XO-1.5 and
 an XO-1.

 Environment started with five XO-1s connected through mesh on channel one.
 Brought up the XO-1.5 (with the new rpms).  It showed me the three new
 icons in Neighborhood.  Clicked on the channel-1 icon - that changed to
 have parentheses around it.  Brought up an os180py XO-1 system (which I
 had a month ago used for testing connection to the XO-1.5).  The os180py
 showed one (not three) local icon in Neighborhood, labeled "Ad-hoc Network
 1".  Clicked on that icon - it got parentheses around it.  Satisfied
 myself that the XO-1.5 and the os180py system cound communicate with each
 other over the ad-hoc network.

 Brought up the XO-1 that had the new rpms applied.  Its Neighborhood
 showed six local icons - three for mesh and three for ad-hoc.  That system
 auto-connected to the "Ad-hoc Network 1".

 I would have preferred that XO-1 to have connected to the existing mesh of
 five XO-1 systems, rather than to the existing ad-hoc of two systems.
 Took system dump.

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

More information about the Bugs mailing list