Line 612: |
Line 612: |
| ::Collections OLPC: http://wiki.laptop.org/go/Collections | | ::Collections OLPC: http://wiki.laptop.org/go/Collections |
| ::'''Testing''' [[Talk:Community/Distributions/Fedora]] | | ::'''Testing''' [[Talk:Community/Distributions/Fedora]] |
− | | + | ::Mesh Networking: (Re: [Testing] [OLPC New Zealand] os873 on XO-1.5 and os873 on XO-1 -07/15/2011) testing@lists.laptop.org 07/18/2011 |
| + | XO-1.5's do not have Mesh networking support, so they use 802.11 Ad-hoc |
| + | networks. XO-1's default to Mesh networks at the moment for compatibility, |
| + | because that is what they historically have done. |
| + | Once an XO-1.5 starts an Ad-hoc network, the XO-1's will spot that network |
| + | within a minute or two, and use the same Mayan numeral as the XO-1.5 to |
| + | indicate its presence. If all the XOs leave an Ad-hoc network it |
| + | disappears; but Network Manager/Sugar cache its presence for a while in case |
| + | a scan accidentally missed a network. |
| + | When an XO-1 sees an Ad-hoc networks they are all filled in as "occupied", |
| + | because an XO-1 does not show the unfilled variants to allow an XO-1 to |
| + | start them. |
| + | This behavior has been around since OLPC build 10.1.3 (860) & Sugar 0.90, |
| + | and is described at http://wiki.sugarlabs.org/go/Features/Ad_hoc_Networking |
| + | I believe XO-1's can be adjusted to default to Ad-hoc as well if desired |
| :http://wiki.laptop.org/go/OS_images | | :http://wiki.laptop.org/go/OS_images |
| :http://wiki.laptop.org/go/Release_notes/10.1.3 | | :http://wiki.laptop.org/go/Release_notes/10.1.3 |