FreeDMR/README.md

FreeDMR Peer Server is a (now very diverged) fork of the hblink3 project

FreeDMR Peer Server - software to assist in building a peer mesh network

Please see the wiki for documentation.

For the single-client SQL importer and dashboard reporting relay, see docs/reporting-relay.md.

For the CPU-sized one-to-five-worker HDStack container deployment and reporting MUX, including the default separate Data Gateway service, see docs/hdstack.md.

See the FreeDMR v1.6.2 release notes before upgrading an existing container deployment. Required deployment migrations are performed by the documented upgrade script; pulling a container image alone does not update mounted configuration.

v1.6.4

The v1.6.4 release notes cover default-enabled unit-data slot protection, optional Gateway admission controls, low-ID service mesh containment and Self Service API fixes. Existing Gateways remain supported. Check that the tag build has succeeded before pulling the stable image.

v1.6.3

The v1.6.3 release notes describe the changes below and the deployment upgrade procedure.

• The standard container can optionally run the SQL exporter under Supervisor, configured with individual REPORT_SQL_* environment variables. It remains disabled by default and supports both single-worker and HDStack deployments.
• RX group-voice END reports optionally include a completed UTF-8 Talker Alias observation, without changing existing report fields. The SQL exporter stores it in a new nullable feed.talker_alias column; add that column before deploying the exporter. See reporting-relay.md.
• The upgrader accepts file-only Data Gateway relationships at the standard /config/data-gateway-relationships.json container path. It requires Python 3 (standard library only) to validate JSON and stops without replacing files when inline and file values conflict or contain invalid JSON. Formatting/key order differences are accepted; custom file paths require manual migration.
• The upgrader prints manual image-update commands even when the deployment configuration is already current. It does not pull or restart containers.
• Fresh installations and legacy D-APRS migrations explicitly set Data Gateway SMS preambles to two. Upgrades preserve existing native Gateway settings; they do not change an operator's configured count or add one when omitted.
• Native Data Gateway links now observe authenticated mesh ingress as well as local HBP traffic, without requiring a connected local recipient. Origin metadata is preserved. Gateway source-quench requests suppress only its group-voice observation copy, never data/control or other routing targets.
• The proxy no longer allocates sessions from standalone DMRA Talker Alias packets. This prevents incompatible alias layouts from creating phantom sessions whose expiry disconnects the real hotspot. Alias packets matching an existing peer session continue to be forwarded unchanged.