[Sugar-devel] [support-gang] Does "wireless missed scans" problem apply in XO-1 to XO-1.5 via ad-hoc ?

[Samuel Greenfeld]

The "Mayan numeral" Ad-hoc icon for a network should appear on a XO-1 --
but only if another nearby computer without mesh capability (such as an
XO-1.5) has connected to that Ad-hoc network first.

There may be a delay before a XO-1 which is configured to default to mesh
networking sees the ad-hoc network is active due to the need to spot it
during a periodic network scan.

But yes it is probably easiest to use an access point.



On Wed, Jun 18, 2014 at 10:32 PM, James Cameron <quozl at laptop.org> wrote:

> On Wed, Jun 18, 2014 at 10:23:05PM -0400, Nathan C. Riddle wrote:
> > Appears XO-1 (13.2.0) cannot connect to XO-1.5 (13.2.0)  as  viewing
> > in Neighborhood View (Mesh).  Specifically, ad-hoc icon does not
> > appear on XO-1 and XO-1 icon does not appear on XO-1.5.   It all
> > works if an XO-1.5 (11.3.0) is also present  and both work
> > individually with XO-1.5 (11.3.0).
> >
> > Is "wireless missed scans" problem playing a role here, where ad-hoc
> > corresponds to AP?
>
> No, the problem you describe is entirely due to the XO-1 using 802.11s
> mesh and the XO-1.5 using 802.11g ad-hoc.  The two methods are
> incompatible and do not interoperate.  This was always the case.
>
> Sugar can be reconfigured on the XO-1 to add the 802.11g ad-hoc icons,
> with consequent confusion for users.  Becomes a question for sugar-devel@
>
> Best is to use an access point.
>
> > (Also, 13.1.0 AU  of XSCE RC1 0.4 on XO-1.5 Neighborhood via init 5
> > appears to be same as using XO-1.5 (11.3.0) )
>
> Not understood, sorry.
>
> --
> James Cameron
> http://quozl.linux.org.au/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140618/4eb3cad6/attachment.html>