#2985 HIGH Trial-3: Need more information in the UI regarding RF/connectivity

[Zarro Boogs per Child]

#2985: Need more information in the UI regarding RF/connectivity
------------------------------+---------------------------------------------
  Reporter:  kimquirk         |       Owner:  dcbw   
      Type:  defect           |      Status:  new    
  Priority:  high             |   Milestone:  Trial-3
 Component:  network manager  |     Version:         
Resolution:                   |    Keywords:         
  Verified:  0                |  
------------------------------+---------------------------------------------
Comment (by Eben):

 Replying to [ticket:2985 kimquirk]:
 > It has been extremely difficult to debug RF, channel and mesh problems
 because we can't see key pieces of information in the UI. It is
 understandable that the connectivity should be transparent and work
 automatically (and we're getting there), but when it doesn't work it is
 really, really hard to figure out what is going on.

 Fair enough.  We actually need more info in any case, but that's being
 discussed in #2866. This ticket sounds more like some temporary testing
 output.

 >  * RF Channel of the mesh or AP to which we are connected or trying to
 connect to

 We can just list the channel as the secondary title of the primary
 palette.

 >  * Whether the mesh is a School Server, or XO MPP, or AP

 I'm not sure I understand this one.  The mesh is, by definition, none of
 the above.

 >  * SSID (already in the UI as tooltext)

 Yup.  This is the primary title of the primary palette, under which the
 channel can be listed for now.

 >  * Whether the mesh or AP has internet connectivity (lowest priority)

 Interesting.  I hadn't really been thinking about having to tell the
 difference between a local network and an actual internet access point.
 How might we illustrate the difference?

-- 
Ticket URL: <https://dev.laptop.org/ticket/2985#comment:2>
One Laptop Per Child <http://laptop.org/>