[Commotion-admin] [commotion-router] Access point and mesh connections not coming up post-setup wizard (#93)

[critzo]

Name: Andy Gunn
Email Address: andygunn at opentechinstitute.org
What type of bug it is? Minor (minor loss of function)
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.

Viewing the "Status" page under the Basic Menu in the Administrator panel. At the top of the page there shows:
commotionAP (On) (Unsecured) (1 Client Connections)
commotionMesh (On) (Secured) (0 Client Connections)

(Ignore the fact that there is no mesh connection - this is another bug filed in another report, that mesh connections do not always connect on boot)
Please describe what behavior you expected:
I expected to see the name of the Access Point and Mesh connection that were named in the Setup stage of configuring the device.
Please describe what behavior you experienced that you believe is wrong:
There should be the actual name of the interfaces that were set during setup, something along the lines of:

Access Point: CassCo.Co-AMP-AP (Unsecured) -- 1 client connected
Mesh Link: Commotion (Secured) -- 0 Neighbor Connections

Also, the format of having information in parentheses is a bit unclear. If the interface is enabled, does it make sense to show it as (on)? Maybe just remove the line if the interface is disabled, since it isn't going to have any connections if it is off.

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