packet:packet_network_monitoring_project
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| packet:packet_network_monitoring_project [2025/11/02 11:31] – g8pzt | packet:packet_network_monitoring_project [2025/11/02 16:18] (current) – [Viewing Packet Traces] g8pzt | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| The purpose of the Packet Network Monitoring Project (PNMP) is to collect packet traces and status reports from all participating nodes, and make them available for network research, monitoring, and fault tracing. | The purpose of the Packet Network Monitoring Project (PNMP) is to collect packet traces and status reports from all participating nodes, and make them available for network research, monitoring, and fault tracing. | ||
| - | The server | + | The idea is to get an overview of the whole network at once. |
| - | [[packet_network_monitoring_project: | + | PNMP is a client-server system. The clients are built into recent versions of XRouter and BPQ nodes. They send JSON-encoded telemetry to the server within UDP datagrams. |
| + | |||
| + | The telemetry consists of AX25 packet header data, node status reports, and details of L2 links and L4 circuits. | ||
| + | |||
| + | The server is at [[https:// | ||
| + | |||
| + | ==== Server Endpoints ==== | ||
| + | |||
| + | AX25 Links Monitor: [[https:// | ||
| + | |||
| + | NetRom L4 Circuits Monitor: [[https:// | ||
| + | |||
| + | Dynamic Network Map: [[https:// | ||
| + | |||
| + | ==== Viewing Packet Traces ==== | ||
| + | |||
| + | You can view the packet traces as seen by each node, via the web API. | ||
| + | |||
| + | Or you can see much more detail using the following command line program: | ||
| + | |||
| + | [[packet_network_monitoring_project: | ||
| + | |||
| + | ==== What Can PNMP Do? ==== | ||
| + | |||
| + | The uses for this project are myriad. | ||
| + | |||
| + | * **Network Monitoring**. For the first time in the history of Packet Radio, we have the potential to " | ||
| + | |||
| + | * **Fault Diagnosis**. Up till now it has been very difficult to diagnose network problems, because such diagnosis required using the (broken) network itself. | ||
| + | |||
| + | * **Fault Alerts**. It would be fairly trivial to monitor the live feed and generate alerts about nodes that suddenly stop reporting their status, links with excessive queue lengths or unusually high retry rates, and so on. | ||
| + | |||
| + | * **Performance Graphs**. These could show things like traffic flows and retry rates over time, which could help to identify diurnal or seasonal problems with QRM, anomalous propagation etc. | ||
| + | |||
| + | * **Network Planning**. By analysing where the traffic is going, where the bottlnecks and single points of failure are, where there is unnecessary connectivity etc. we can plan better network connections. | ||
| + | |||
| + | ==== How To Enable Telemetry on Your Node ==== | ||
| + | |||
| + | * **If you run XRouter:** XRouter has been automatically sending telemetry since v504j, allowing the system to be developed and refined. But for best results, please update to version 504m. If you wish to DISABLE telemetry, please add the following directive to XROUTER.CFG: | ||
| + | |||
| + | * **If you run BPQ:** Firstly, you need to be running version 6.0.25.9. Then, because the client is disabled by default, you need to add the following directive to your bpq configuration file: " | ||
| + | |||
| + | |||
| + | (to be continued) | ||
packet/packet_network_monitoring_project.1762083070.txt.gz · Last modified: by g8pzt
