Informal survey on operator's use of the node's web interface

1)  Check status of "normal" connections.
2)  Firmware updates (I install almost every nightly build).
3)  Verify DHCP assignments
4)  Change advertised services

 

1. Monitor/check mesh status
2. Monitor/check  node status 
3. Administration - firmware updates usually, sometimes packages

The above is once the node is set up and operational, obviously.

If I could make one request for a feature in a new UI it would be to have all of the destination pages listed, say on the left, so you don't have to navigate to one page to get to another, e.g. node status to get to mesh status, setup to get to administration, etc. The current hierarchy is logical, but once you know what all the pages are it just adds an extra step. This is not a big deal, but I think it would be a sensible refinement. The way the documentation is organized in the readthedocs.io page is a good example.

73, Rob KG7LMI
 

1. Check node's status
2. Check mesh performance status, by whether and how quickly the node page loads
3. Check the mesh status to ensure expected nodes are connected and to see if any new nodes have connected
4. Spot-check the SNR of connected nodes (done less frequently for established node links)
5. Check what channel remote nodes are on for adding nodes to mesh
6. Perusing the mesh status page to see what services are out there including to get ideas on what services I might want to add
 

1) Check Mesh Status, (would like to be able to sort by Call Sign)
2) DHCP Services (with description of service, not just name of service) and leases
3) Performance graphs
4) Save changes and reboot on main screen (node status).
5) Additional all the existing main screen (node status) selections and info.