Difference between revisions of "Mesh/Firmware"
added LightSquid
(changed formatting) |
(added LightSquid) |
||
| Line 84: | Line 84: | ||
:Ideally we could list/graph the number of people who have associated with your mesh node. | :Ideally we could list/graph the number of people who have associated with your mesh node. | ||
:We could also just list/graph the up/down data of people who have been using the mesh. | :We could also just list/graph the up/down data of people who have been using the mesh. | ||
* [http://lightsquid.sourceforge.net LightSquid] (used by pfSense) | |||
*Set location, name, description. | *Set location, name, description. | ||
:But do you want to know the location centrally as well so that you can display nodes on the map? Will people enter this information twice or will you pull this information from nodes and then display on the map? Same for name and description. I would suggest that information is stored only once. In your case on the node itself. So probably you can then pull this information through nodewatcher scripts on nodes and then display nodes the map. Just really should not require people to enter or maintain information on two places because it desyncs very fast. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT) | :But do you want to know the location centrally as well so that you can display nodes on the map? Will people enter this information twice or will you pull this information from nodes and then display on the map? Same for name and description. I would suggest that information is stored only once. In your case on the node itself. So probably you can then pull this information through nodewatcher scripts on nodes and then display nodes the map. Just really should not require people to enter or maintain information on two places because it desyncs very fast. [[User:Mitar|Mitar]] ([[User talk:Mitar|talk]]) 22:20, 24 July 2013 (PDT) | ||