I recently set up an M17 ↔ AllStarLink bridge on a Raspberry Pi running AllStarLink/Debian 13.
The setup uses a separate AllStar private node dedicated to M17, while my other private node remains dedicated to DVSwitch. This keeps the M17 bridge independent from the existing DVSwitch/Analog_Bridge setup.
Basic architecture
AllStar radio node → AllStar M17 bridge node → USRP2M17 → M17 reflector
The bridge supports communication in both directions:
- AllStar → M17
- M17 → AllStar
- M17 reflector connection/disconnection
- DTMF control for reflector switching
- M17 callsign/destination handling
- Web browser dashboard for monitoring and controlling the M17 connection
The web dashboard provides a convenient way to see the current M17 reflector and activity, including M17 callsigns and destinations.
The DTMF control concept was inspired by the Digital_Link project on GitHub from William M. Mongan, with the necessary adaptations for the AllStarLink/M17 setup.
The setup required configuring USRP2M17, AllStar routing, audio between the two systems, M17 reflector connectivity, DTMF control, and the web dashboard.
I meant more that M17 is open and not controlled by a manufacturer. DMR itself is an open standard, even though most DMR implementations and ecosystems are manufacturer-specific.
