[Commotion-admin] [commotion-router] Confirm mesh connections work correctly (#107)

[critzo]

This issue is likely fixed (likely cause was BSSID issue) but needs to be confirmed in testing. Originally submitted to the Commotion website by @andygunn in post-testing of the 1.0 release.

**What were you doing on the device right before and when the error occurred?**
This bug involved a test connection between two Commotion nodes - a NanoStation M2 and a PicoStation M2, in close proximity (~25 feet apart). Two fresh TFTP factory installs were performed on the equipment, with Commotion version 1.0, downloaded Tuesday January 14th.

The two devices were set up, side-by-side, with identical mesh connection information. They were configured with different hostnames, APs, etc, but all mesh information (SSID, channel, password) were set identically.

**Please describe what behavior you expected:**
We expected the devices to create a mesh connection between the devices.

**Please describe what behavior you experienced that you believe is wrong:**
The devices will not mesh reliably if they are set with an encrypted connection. We experimented with various changes, and were able to mesh the devices together, but without consistent results. An example:

The two routers had encrypted mesh connections enabled, but would not connect. After disabling the encryption password on the mesh connection, they would mesh. We then re-enabled the encryption password, and the routers were able to mesh. After rebooting one of the devices, it meshed.

We then performed a reset to defaults on one of the devices (after encountering a different bug), reconfiguring and rebooting, and they do not mesh.

---
Reply to this email directly or view it on GitHub:
https://github.com/opentechinstitute/commotion-router/issues/107
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-admin/attachments/20140219/c804e537/attachment.html>