<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 08.00.0681.000">
<TITLE>RE: [Server-devel] Collaboration XO-1 with XS</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Hi James,</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">I have been</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">fairly</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> familiar</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">some time</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">with using the basic default installation of the XS. It is</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">specifically the</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> combination</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">of</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> XO-1 build 883 / Sugar 0.94.1 with XS0-0.6 which</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">has thrown up some issues</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">-</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">with collaboration.</FONT></SPAN><SPAN LANG="en-nz"> </SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">A typical situation when we observe this</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> recently</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">: a workshop with 20 teachers, all who have freshly installed release 11.3.0 on their XO-1s</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> and registered on the workshop XS and restarted. All have been accessing the Moodle pages with no problems and the links to the public content in the /library folder.</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> I</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">will</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">have been using the XS network</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"></FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">wirelessly to an XO that is running Classroom Broadcast Activity</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">, with no difficult whatsoever</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">. So there is no need to ping the server to understand that the XOs</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">are all properly connected and registered, although I take your point and would have done more</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">diagnostics</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> if i knew how to isolate the issue with the collaboration problem we experienced.</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">We were able to replicate the issue on identically set-up servers. The issue is</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">:</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"></FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">not all the other connected XOs appear in the neighbourhood view, and when trying to demonstrate collaboration using the set up above, it was only rarely that the "sharing" icon appeared on other XOs</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">neighbourhood</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> view eve</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">n though all else seemed to be working fine.</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"></FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">I tried using the discard network history with a few XOs</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">only once</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">at the end of the workshop</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">, and we then run out of time. I tried again with my own setup later, using two XOs only, and replicated the issue but the discard history did not work then. So that</FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas">might not be useful information.</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> </FONT></SPAN><SPAN LANG="en-nz"> <FONT FACE="Consolas"></FONT></SPAN><SPAN LANG="en-nz"> </SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Perhaps I should rephrase my question:</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Was it intended that collaboration should work with XO-1s running rel</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">ease 11.3.0 using the XS-0.6 default installation?</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Secondary question, if this is not working, and I have made no customisation other than add some links using aliases presented as</FONT></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas"> links on the Moodle home page, what can I do to trouble shoot?</FONT></SPAN><SPAN LANG="en-nz"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"></SPAN><SPAN LANG="en-nz"><FONT FACE="Consolas">David Leeming</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"></SPAN><SPAN LANG="en-us"><FONT FACE="Consolas">-----Original Message-----<BR>
From: quozl@us.netrek.org [<A HREF="mailto:quozl@us.netrek.org">mailto:quozl@us.netrek.org</A>] On Behalf Of James Cameron<BR>
Sent: Friday, 27 April 2012 7:39 a.m.<BR>
To: David Leeming<BR>
Cc: 'XS Devel'; 'OLPC Devel'<BR>
Subject: Re: [Server-devel] Collaboration XO-1 with XS</FONT></SPAN><SPAN LANG="en-nz"></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">On Fri, Apr 27, 2012 at 06:38:00AM +1000, David Leeming wrote:</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">> [...] we work around it by for instance using ?discard network</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">> history? which seems to help.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">I was deeply involved in the "discard network history" feature at one</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">point in development, and at the time the only thing it did was to</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">remove access point names (ESSIDs) from the list of known access points.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">I've just checked the code and that is still only what it does.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">So I'm surprised it is having an effect. But congratulations for</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">finding it does have an effect.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">I know nothing about the network at the location. Is there more than</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">one access point name available?</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">If so, at the time of the problem, the reason the button is having an</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">effect may be because a disconnection has led to the laptop associating</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">with another access point, and pressing the button would prevent that.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">If not, then the button is only serving to disconnect the laptop from</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">the network. You may find the same effect to occur by clicking on the</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">access point in the network neighbourhood view.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Lastly, whether activities are open at the time of the forced disconnect</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">and reconnect may be interesting.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">Next time, please do some technical diagnosis at the time of the problem</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">... use Terminal activity to ping the server. As I have recently seen</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">examples of TP-Link with OpenWRT access points that silently block data</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">flow, it reminds me that some diagnosis is worth doing. In the cases I</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">observed, data flow was restored by reconnecting. That you currently</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">reconnect to work around the problem may be a coincidence, or it might</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">be this same kind of problem.</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">-- </FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas">James Cameron</FONT></SPAN></P>
<P DIR=LTR><SPAN LANG="en-nz"><FONT FACE="Consolas"><A HREF="http://quozl.linux.org.au/">http://quozl.linux.org.au/</A></FONT></SPAN></P>
</BODY>
</HTML>