<div dir="ltr">Hi All<div><br></div><div>It does appear (caveat: based on some _limited_ testing I have done today) that switching off the XO-1 mesh networking will allow the XOs to connect reliably to APs. </div><div><br>
</div><div>We can see that the 'last beacon' times immediately return to normal when mesh is disabled on all the XOs. </div><div><br></div><div>The mesh operation can be disabled with the command :</div><div> sudo echo 0 > /sys/class/net/eth0/lbs_mesh</div>
<div><br></div><div>This command can be added to /etc/rc.d/rc.local so that it is executed on start up as the change is not persistent. Also needs to be done somewhere in power.d for resume.</div><div><br></div><div>It must be noted however that mesh has to be switched off on *every* XO-1 in the area.</div>
<div>If even one XO-1 has mesh enabled, all the other XOs will have a problem connecting.</div><div><br></div><div>Also, of course, there is no mesh networking available between XOs, so an AP has to be present for the XOs to collaborate.</div>
<div><br></div><div>I understand that some past implementations have disabled mesh for various reasons, but it is obviously not a general solution.</div><div><br></div><div>A more general solution will require a greater understanding of the XO-1 mesh facility and some modification of it to make it more 'sociable'.</div>
<div><br></div><div>Regards</div><div>Terry<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Feb 8, 2014 at 5:25 PM, Bernie Innocenti <span dir="ltr"><<a href="mailto:bernie@codewiz.org" target="_blank">bernie@codewiz.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've seen XO-1s randomly drop off the AP in Paraguay.<br>
<br>
I *think* we solved it by disabling 802.11s (the mesh network). This can<br>
be done at boot time by setting a parameter of the libertas kernel module.<br>
<br>
Sorry for being vague, it's been a long time ago.<br>
<br></blockquote><div><br></div></div></div></div></div>