packet:network-monitoring-project
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| packet:network-monitoring-project [2025/11/02 11:15] – created m0lte | packet:network-monitoring-project [2025/11/02 11:23] (current) – [What We Need From You] m0lte | ||
|---|---|---|---|
| Line 167: | Line 167: | ||
| ---- | ---- | ||
| + | |||
| + | ===== Other Packet Systems & Future Clients ===== | ||
| + | Right now the service has first-class, | ||
| + | |||
| + | But the service is **not limited to those two.** If you run any of the following, you are very much invited to send data: | ||
| + | |||
| + | * **JNOS / JNOS2** (Linux, classic net/ROM + BBS environments) | ||
| + | * **TheNet / TheNet-derived nodes** (older but still on air in some areas) | ||
| + | * **FlexNet-style nodes** | ||
| + | * **Linux-based packet stacks using kissattach/ | ||
| + | * **Direwolf-based nodes** that are already doing APRS/AX.25 and have access to link/ | ||
| + | * **Custom / Pi-based nodes** people have built for local RF + IP tunnelling | ||
| + | |||
| + | At the moment these systems are **not** sending telemetry to the monitoring service simply because **nobody has written the small client for them yet.** The service itself is happy to accept the data — it just needs it in the expected format. | ||
| + | |||
| + | What we need from the wider packet community: | ||
| + | |||
| + | * someone with a **JNOS** system to add a lightweight exporter; | ||
| + | * someone who still runs **TheNet / FlexNet** to see what info is available from the node and map it to the telemetry fields (node ID, neighbours, links, circuits/ | ||
| + | * people maintaining **modern Linux packet gateways** to add a tiny script/ | ||
| + | * anyone writing **Node-RED / Python / Go** tooling to publish events via MQTT-over-WS straight to the service. | ||
| + | |||
| + | In other words: **if your packet stack can tell you “who I am”, “who I’m connected to”, and “what sessions I have”, then it can probably send telemetry to this service.** The data is most welcome — the more diversity of nodes we see, the better the global picture becomes. | ||
| + | |||
| ===== For Developers ===== | ===== For Developers ===== | ||
| Line 197: | Line 221: | ||
| ===== Ideas to Build Today ===== | ===== Ideas to Build Today ===== | ||
| - | * **Live topology map** | ||
| - | * Draw only nodes with recent activity | ||
| - | * Fade nodes that have gone quiet | ||
| - | * Flash or animate links when a circuit is established | ||
| - | * Distinguish RF vs Internet links (the site already does this) | ||
| * **Path watcher / path canary** | * **Path watcher / path canary** | ||
| Line 253: | Line 272: | ||
| ===== What We Need From You ===== | ===== What We Need From You ===== | ||
| * **If you run Xrouter (PZT):** check you are on a version where this is on by default, make sure the target host/port is reachable, and confirm you appear on the front end and on the Network Map. | * **If you run Xrouter (PZT):** check you are on a version where this is on by default, make sure the target host/port is reachable, and confirm you appear on the front end and on the Network Map. | ||
| - | * **If you run BPQ (BPQ32):** enable the telemetry in config (it is OFF by default), restart, and check the front end and Network Map. | + | * **If you run BPQ (BPQ32): |
| * **If you write software / run Node-RED / like dashboards: | * **If you write software / run Node-RED / like dashboards: | ||
| * **If you spot gaps:** open issues or PRs on GitHub: https:// | * **If you spot gaps:** open issues or PRs on GitHub: https:// | ||
packet/network-monitoring-project.1762082149.txt.gz · Last modified: by m0lte