#6287 NORM Never A: Associating with one mesh prevents you from successfully associating with a different one.

[Zarro Boogs per Child]

#6287: Associating with one mesh prevents you from successfully associating with a
different one.
------------------------------+---------------------------------------------
  Reporter:  cscott           |       Owner:  dcbw          
      Type:  defect           |      Status:  new           
  Priority:  normal           |   Milestone:  Never Assigned
 Component:  network manager  |     Version:                
Resolution:                   |    Keywords:                
  Verified:  0                |    Blocking:                
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by wad):

 It's not as simple as indicated above.  I have been successful at changing
 from one mesh to another in the past --- but I've also noticed that some
 amount of time (usually after the laptop has been running for longer than
 a day) a laptop cannot associate with a "new" mesh (even on the same
 channel it was earlier).

 When this happens, the server usually indicates that DHCP discoveries were
 received and responded to, but the laptop claims not to have received
 them.  Killing Network Manager and manually attempting to connect doesn't
 work either in these cases.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6287#comment:1>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system