KB8PMY
/
FreeDMR
mirror of http://gitlab.hacknix.net/hacknix/FreeDMR.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
FreeDMR/docs/release-notes-v1.6.4.md

4.7 KiB
Raw Permalink Blame History

FreeDMR v1.6.4 release notes

This maintenance release adds server-side unit-data protection and prepares FreeDMR for optional Gateway admission queueing. Existing Data Gateway and D-APRS deployments remain supported; no Gateway or Kryten upgrade is required to use FreeDMR v1.6.4.

Changes

  • Unit-data slot protection is enabled by default, including configurations that omit UNIT_DATA_HOLD. Admitted outbound unit data holds its destination slot for the same source/destination pair until five seconds of inactivity. Competing network voice/data and generated prompts cannot interrupt that hold. Existing voice-start admission and voice hangtime checks still apply.
  • Added link-local BCRQ/BCTS request-to-send controls on the dedicated authenticated DATA-GATEWAY FBP5 relationship. A successful request reserves a local slot for 500ms until matching data starts. Ordinary mesh links cannot request holds. Existing FBCP controls and DMR packet bytes are unchanged.
  • Unit-data mesh forwarding now requires both the RF source and destination DMR IDs to be at least 1000000. Requests and replies involving low service IDs, including 5000, 5005 and 900999, remain local. Local HBP delivery and the dedicated Gateway observation feed are unchanged. Subscriber-to-subscriber data remains eligible for mesh forwarding.
  • Added /api/v1/peer/dial for dashboard Self Service using the connected hotspot/repeater's OPTIONS key. Existing backend Dial authentication, connected-peer, slot, RF-busy, timer and voice-announcement checks remain.
  • API authentication rejects absent, empty and non-string keys even when the configured key is missing. The API still requires a protected deployment; this does not make the whole API suitable for public exposure.

Compatibility And Configuration

The slot hold benefits existing SMS delivery immediately. It is not an RF reservation, a bidirectional lock or a delivery guarantee. It neither queues packets nor stops an RF station transmitting. The hold is measured from the last admitted network burst, not RF completion. Continuous data can retain the slot; packet-count fairness is not implemented. Generated prompts suppressed by a hold are cancelled, not replayed afterwards.

To retain the previous admission behaviour on an access master, set:

UNIT_DATA_HOLD: False

Request/grant queueing additionally needs a compatible Gateway. Its SMS opt-in is FREEDMR_GATEWAY_SMS_ADMISSION=true; leave that disabled on older workers. API consumers must support the Gateway's queued message state. An older Gateway may continue submitting unreserved SMS as before. No coordinated mesh upgrade is required. See unit-data-hold.md.

The low-ID rule applies to unit-data forwarding, not group voice. It is an address-based routing rule, not IP payload inspection or authenticated ownership of a DMR ID. Deployments intentionally sending low-source-ID unit data between servers must account for this change before upgrading.

For the Self Service endpoint, see api.md. This release does not enable the API, expose a new port or alter container topology automatically.

Upgrade And Images

Back up configuration and state. An existing deployment already migrated for v1.6.3 needs no new deployment marker, schema migration or installer change for v1.6.4. Older deployments should follow the v1.6.3 upgrade instructions first. Preserve each component's selected image channel and update only the intended services.

The tag build publishes latest, v1.6.4-with-proxy and development-latest for Linux AMD64, ARM64, ARMv7 and i386. Wait for the tag pipeline to succeed before pulling release images. Publication does not deploy or restart servers.

Validation And Limitations

The development image passed 236 regression tests on Hawk. The opt-in Dial UDP test and the two-worker HDStack UDP test also passed; the latter was updated to wait for the new five-second data hold before checking voice.

Isolated Hawk tests with real Linux TUN and UDP verified bidirectional IP, busy-slot deferral, protection from competing voice, confirmed/unconfirmed Kryten SMS echoes, no-route rejection and mesh containment. Positive controls verified that ordinary subscriber data and group voice still reached the simulated mesh peer. Live services were not changed by these tests.

This is amd64 software-path validation, not new live RF or ARM runtime validation. Experimental IP Gateway deployment is separate from this release. DMR SMS remains a best-effort amateur service affected by RF loss, frequency offset, busy channels and terminal interoperability. Reports of problems, including radio model, SMS format and confirmed/unconfirmed mode, are welcome.

Powered by TurnKey Linux.