Changes

Jump to navigation Jump to search
m
→‎Jabber: The Server/Prosody: Ad-Hoc and Mesh Networking
Line 33: Line 33:  
*Technical: Jabber setup
 
*Technical: Jabber setup
 
: [[The Server/Prosody]]
 
: [[The Server/Prosody]]
 +
===Ad-Hoc and Mesh Networking===
 +
*Collaboration on Ad-hoc Networking must be initiated by XO-1.5 when connecting to an XO-1
 +
::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 -Samuel Greenfield
 +
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
 +
 +
*Enable Ad-hoc network on XO-1
 +
(Re: [Testing] [OLPC New Zealand] os873 on XO-1.5 and os873 on XO-1 -07/23/2011) -Gary Martin
 +
1) You can enable ad-hoc networking on recent XO-1 builds with (your neighbour hood view will be populated with the three new Mayan numbered adhoc icons as well as the usual three mesh icons):
 +
gconftool-2 -s  /desktop/sugar/network/adhoc -t bool true
 +
2) Unfortunately I am not aware of current builds properly supporting disabling
 +
(e.g. a gconf setting would be nice) mesh network on XO-1 hardware…
 +
There was talk and some patches floating about, but I'm not sure anything landed.
 +
The closest seems to be the below terminal command, but it does not survive a power cycle, or sleep/wake cycle :
 +
( Maybe there is some power script this could be added to for folks who want to disable mesh permanently (until we get something more elegant in place for the future)?
 +
su
 +
echo 0 > /sys/class/net/eth0/lbs_mesh
 +
 +
*07/23/2011 IRC:#sugar
 +
<silbe> Sugar will use link-local collaboration (telepathy-salut), using multicast on the LAN (e.g. wifi).
 +
If a Jabber server is configured, Sugar will try to connect to it (using telepathy-gabble).
 +
As soon as the Jabber connection has been established, Sugar will deactivate the link-local collaboration.
12,355

edits

Navigation menu