c47214fc49
Is not maintained any more |
||
---|---|---|
cmd | ||
contrib | ||
data | ||
database | ||
jsontime | ||
meshviewer | ||
respond | ||
rrd | ||
runtime | ||
webserver | ||
.gitignore | ||
.gitmodules | ||
.test-coverage | ||
.travis.yml | ||
config_example.toml | ||
INSTALL.md | ||
README.md |
Yanic
__ __ _
\ \ / /_ _ _ __ (_) ___
\ V / _` | '_ \| |/ __|
| | (_| | | | | | (__
|_|\__,_|_| |_|_|\___|
Yet another node info collector
yanic
is a respondd client that fetches, stores and publishes information about a Freifunk network. The goals:
- Generating JSON for Meshviewer
- Storing statistics in InfluxDB to be analyzed by Grafana
- Provide a little webserver for a standalone installation with a meshviewer
Usage
Usage of ./yanic:
-config path/to/config.toml
Configuration
Read comments in config_example.toml for more information.
Live
- meshviewer Freifunk Bremen with a patch to show state-version of
nodes.json
- grafana Freifunk Bremen show data of InfluxDB
How it works
In the first step Yanic sends a multicast message to the group ff02:0:0:0:0:0:2:1001
and port 1001
.
Recently seen nodes that does not reply are requested via a unicast message.
Related projects
Collecting data from respondd:
- HopGlass Server written in Node.js
Respondd for servers:
- ffnord-alfred-announce from FreiFunkNord
- respondd from Sunz3r