Associating with one mesh prevents you from successfully associating with a different one.

[cscott]

Tested on update.1-690 and schoolservers on channels 1 and 6.

Initially connected to the schoolserver on channel 6. Trying to then connect to mesh 1 appeared to succeed, but in fact the machine remained on channel 6, using channel 6's dns server. Couldn't reach the outside world.

[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.

[wad]

Witnessed the same behavior today. Took two B4 laptops, with fresh installs of build 697. After their first boot, both were associated with channel 1 in simple mesh mode. When I clicked on channel 6, one associated and immediately found the school server, and the other didn't. After several attempts to get the latter to associate (it went to the right channel, but didn't find the school server) I rebooted it. After reboot it found the school server on channel 6 fine.

[gregorio]

Milestone Never Assigned deleted