#10246 NORM Not Tri: XO-1.5 -- add mesh capability

[Zarro Boogs per Child]

#10246: XO-1.5 -- add mesh capability
--------------------------+-------------------------------------------------
 Reporter:  mikus         |                 Owner:                                   
     Type:  enhancement   |                Status:  new                              
 Priority:  normal        |             Milestone:  Not Triaged                      
Component:  not assigned  |               Version:  Development build as of this date
 Keywords:                |           Next_action:  never set                        
 Verified:  0             |   Deployment_affected:                                   
Blockedby:                |              Blocking:                                   
--------------------------+-------------------------------------------------
 Each time I install a build, I upgrade it with all available more-recent
 RPMs (e.g., NetworkManager, sugar, etc.).

 Installed os207 (and upgraded it).  Clicked in Neighborhood View on the
 "olpc-mesh" icon shown there.  The system connected (channel 1), and added
 my local os180py XOs to Neighborhood View.  I was able to successfully use
 a Chat session between the os207 system and an os180py system.

 What I found interesting was that there were other XOs in the room with
 active "mesh" connections on channel 1 -  but those were NOT being seen in
 the os207 Neighborhood View (nor did those XOs see the os207 system).

 ----

 The principal difference I noted was that these other XOs each had
 interface msh0 in 'Repeater' mode (and interface eth0 in 'Managed' mode),
 whereas the os207 system did NOT have any interface msh0.  The os207
 system did have interface eth0, which was set up in 'Ad-Hoc' mode.  And
 the os180py systems also happened to have their interface eth0 set up in
 'Ad-Hoc' mode.  My conclusion -- when there is a "mode match",
 collaboration can take place.

 What is needed is for the XO-1.5 (e.g., os207) to support modes in
 addition to 'Managed' and 'Ad-Hoc'.

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