#3593 BLOC Trial-3: Mesh channel randomization breaks NM 'mesh-start' tweakable

[Zarro Boogs per Child]

#3593: Mesh channel randomization breaks NM 'mesh-start' tweakable
------------------------------+---------------------------------------------
  Reporter:  dcbw             |       Owner:  jg     
      Type:  defect           |      Status:  new    
  Priority:  blocker          |   Milestone:  Trial-3
 Component:  network manager  |     Version:         
Resolution:                   |    Keywords:         
  Verified:  0                |  
------------------------------+---------------------------------------------

Comment(by AlexL):

 Things seem to be working fine. With local in the mesh-start file, the
 laptop connect to a local mesh every time I rebooted it, even after
 connecting to the media lab and rebooting. I did not try connecting link
 local in an environment without any access points or mesh portals, but I
 think other people have already done that test, and I'll try it on the
 train home today, reporting only if it goes badly.

 Issue: I experienced one weird occurrence was with entering infra in the
 mesh-start file. It connected to the media-lab AP on reboot, as it should.
 However, if I then click on mesh 1, everything besides that XO disappears
 from the mesh view. The laptop is no longer connected to the web, but it
 can still be seen by other XO's on the media lab AP. If the mesh-start
 file is deleted, than everything works normally. As no user will be doing
 this, it's not really a problem, but it would probably a good thing to
 understand why this occurs.

-- 
Ticket URL: <https://dev.laptop.org/ticket/3593#comment:9>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system