Use meshviewer backend from vpn01.freifunk-vogtland.net

FreifunkVogtland / ffv-meshviewer-config

Configuration file for the FFV Mesh-Viewer

1 stars 1 forks source link

Use meshviewer backend from vpn01.freifunk-vogtland.net #4

Closed ecsv closed 8 years ago

ecsv commented 8 years ago

The split between FFC and FFV is planned. Thus we should stop using their server to gather the node data. Instead use vpn01.freifunk-vogtland.net for this task.

SunboX commented 8 years ago

👍

ecsv commented 8 years ago

On Montag, 26. September 2016 07:29:57 CEST André Fiedler wrote:

XMLHttpRequest cannot load http://meshviewer.chemnitz.freifunk.net/ffv/nodes.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://vogtland.freifunk.net' is therefore not allowed access.

Why is your error message still showing meshviewer.chemnitz.freifunk.net? And vpn01.freifunk-vogtland.net returns

Access-Control-Allow-Origin:*

ecsv commented 8 years ago

Same for meshviewer.chemnitz.freifunk.net:

wget -S http://meshviewer.chemnitz.freifunk.net/ffv/nodes.json
--2016-09-26 16:33:19--  http://meshviewer.chemnitz.freifunk.net/ffv/nodes.json
Resolving meshviewer.chemnitz.freifunk.net (meshviewer.chemnitz.freifunk.net)... 2001:4ba0:fffa:123::, 5.199.142.119
Connecting to meshviewer.chemnitz.freifunk.net (meshviewer.chemnitz.freifunk.net)|2001:4ba0:fffa:123::|:80... connected.
HTTP request sent, awaiting response... 
  HTTP/1.1 200 OK
  Date: Mon, 26 Sep 2016 14:33:19 GMT
  Server: Apache/2.4.10 (Debian)
  Last-Modified: Mon, 26 Sep 2016 14:33:10 GMT
  ETag: "436a0-53d6a01d691e2"
  Accept-Ranges: bytes
  Content-Length: 276128
  Access-Control-Allow-Origin: *
  Content-Type: application/json
  Keep-Alive: timeout=5, max=100
  Connection: Keep-Alive

SunboX commented 8 years ago

Was my fault, I think it was cached by my Browser. Sry. ;) Seems to work now.

Only thing left is to set up the Grafana Stats / Monitoring right?

ecsv commented 8 years ago

having all remaining nodes flashed to b20160923-v or higher (currently not possible because many are offline or some have auto update disabled + SSH keys disabled)
IPv6 uplink + RA for clients (maybe over Freifunk Rheinland backbone - but this takes time)
private FFV-IPv4-Range instead of using the one from FFC (required for InterCity-VPN; will also requires another firmware update to fix AnyCast address)
InterCity-VPN
private DHCP IPv4 range/pool for each server
Grafana+Graphite
...

This is all entangled because we don't want to loose too many services but also don't want to interrupt the services from FFC. But for example the setup of an Grafana server can already be done by an interested individual/group.