Differences

This shows you the differences between two versions of the page.

--- packet:network-monitoring-project [2025/11/02 11:15] – created m0lte
+++ packet:network-monitoring-project [2025/11/09 21:53] (current) – [Configuration: Xrouter (G8PZT)] m0lte
@@ Line 118: / Line 118: @@
 **Status:** default-on
-**(Paula’s section will go here.)**
+See [[packet_network_monitoring_project|Paula's write-up]]
-Suggested content for Paula:
+----
-  * Which Xrouter versions/builds have this telemetry already baked in
+===== Configuration: BPQ (G8BPQ) =====
-  * What, if anything, the sysop needs to set (host, port, interval)
+**Status:** default-off — you must enable it.
-  * How to confirm from Xrouter logs that it has sent an update
-  * How to confirm on **https://node-api.packet.oarc.uk/** that the node is listed
-  * Recommended reporting interval / not being too chatty
-  * Notes about also talking to the *mapping API* (this monitoring service is separate but complementary)
-Example structure Paula could use:
+Obtain latest testing binary, or build from github source
+in your bpq32.cfg:
-  *Prerequisites*
+<code>
-  *Configuration block / commands*
+ENABLEOARCAPI=1
-  *Restart / reload instructions*
+</code>
-  *How to verify on the web front end (including the Network Map)*
-  *How to back off reporting if bandwidth is tight*
-(Replace this whole subsection with Paula’s real notes.)
 ----
-===== Configuration: BPQ (G8BPQ) =====
+===== Other Packet Systems & Future Clients =====
-**Status:** default-off — you must enable it.
+Right now the service has first-class, “known good” support for **Xrouter (G8PZT)** and **BPQ/BPQ32 (G8BPQ)** because those are the two stacks whose authors have actively helped push telemetry out.
-**(John’s section will go here.)**
+But the service is **not limited to those two.** If you run any of the following, you are very much invited to send data:
-Suggested content for John:
+  * **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/ax25d** with their own routing glue
+  * **Direwolf-based nodes** that are already doing APRS/AX.25 and have access to link/session info
+  * **Custom / Pi-based nodes** people have built for local RF + IP tunnelling
-  * The minimal parameter(s) to add to BPQ to start sending telemetry
+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.
-  * How to verify BPQ has actually sent a packet to the monitoring service
-  * Notes for sysops behind NAT/firewalls (allow outgoing UDP to the service)
-  * Recommended reporting interval
-  * A quick “disable” / “rollback” line in case someone wants to stop sending
-  * How to check on **https://node-api.packet.oarc.uk/** that it worked
-  * How to confirm the node is now visible on **Network Map** (if link data is present)
-Example structure John could use:
+What we need from the wider packet community:
-  *Add this to BPQ config:*
+  * someone with a **JNOS** system to add a lightweight exporter;
-  *Restart BPQ:*
+  * 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/sessions if present);
-  *Check the front end:*
+  * people maintaining **modern Linux packet gateways** to add a tiny script/daemon that emits telemetry on a timer;
-  *Check Network Map:*
+  * anyone writing **Node-RED / Python / Go** tooling to publish events via MQTT-over-WS straight to the service.
-  *If you don’t see it, check firewall:*
-(Replace this whole subsection with John’s real notes.)
+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 =====
@@ Line 197: / Line 187: @@
 ===== 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**
@@ Line 253: / Line 238: @@
 ===== 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 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):** upgrade, enable the telemetry in config (it is OFF by default), restart, and check the front end and Network Map.
   * **If you write software / run Node-RED / like dashboards:** grab the OpenAPI spec, or subscribe to MQTT-over-WS, and build *something*.
   * **If you spot gaps:** open issues or PRs on GitHub: https://github.com/M0LTE/node-api