Freifunk-Troisdorf/yanic
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
151 Commits 9 Branches 2 Tags 720 KiB
Go 97.1%
Python 2.3%
Shell 0.6%
38f32952c2
Go to file
Geno 38f32952c2 Merge pull request #5 from FreifunkBremen/nodes_expiration 
Expire nodes after n days of inactivity
(Ist okay so -> gleich mal ein Test auf meiner Maschine ...)
2016-10-09 18:49:31 +02:00
api api aliases delete cleanup 2016-07-13 00:09:49 +02:00
data Remove contact from nodes.json 2016-10-07 22:46:59 +02:00
database fix bugs after refactoring 2016-10-04 14:54:19 +02:00
jsontime Expire nodes after n days of inactivity 2016-10-08 10:51:31 +02:00
meshviewer Remove indirection of Flags 2016-10-08 12:06:47 +02:00
models Add test for node expiration 2016-10-08 12:06:47 +02:00
respond fix bugs after refactoring 2016-10-04 14:54:19 +02:00
rrd fix bugs rrd importer -> clients are no nodes :) 2016-10-04 15:00:54 +02:00
.gitignore airtime + no panic on lost of influxdb connection 2016-07-04 14:46:45 +02:00
.gitmodules switch to config-file 2016-03-07 09:52:52 +01:00
.test-coverage Add Coveralls 2016-03-20 13:51:54 +01:00
.travis.yml Update go versions for Travis 2016-10-07 22:51:58 +02:00
config_example.yml Expire nodes after n days of inactivity 2016-10-08 10:51:31 +02:00
main.go Use defer 2016-10-04 00:50:39 +02:00
README.md Add related projects 2016-03-21 22:53:45 +01:00

README.md

Respond Collector

Build Status Coverage Status

respond-collector is a respond client that fetches, stores and publishes information about a Freifunk network. The goals:

  • Generating JSON for MeshViewer (Works with branch JSONv2)
  • Storing statistics in InfluxDB to be analyzed by Grafana
  • Provide information via Websocket- and JSON-APIs

Usage

Usage of ./respond-collector:
  -config path/to/config.yml

Development

respond

It send the gluon-neighbour-info request and collect them together.

It will send UDP packetes by the multicast group ff02:0:0:0:0:0:2:1001 and port 1001.

modes.Nodes

It cached the Informations of the Nodes and will save them periodical to a JSON file. The current nodes are saved default under nodes.json.

websocketserver

One Instance is running under /nodes which send updates or new Nodes, which are collected by respond.

Issues

Later there should be also /aliases Websocket with Authentification to manage the aliases.json with the request for changes.

Related projects

Collecting data from respondd:

Respondd for servers: