Supported Modes

Vexillum is a multi-protocol amateur radio reflector runtime.

A Vexillum-powered reflector may support several radio voice modes from one system. The exact modes available depend on what the reflector operator has enabled.

Mode overview

Mode	Description	Typical user equipment
D-Star	D-Plus, DExtra, or DCS-style reflector access	D-Star radios, hotspots, gateways
DMR	DMR reflector-style connectivity	DMR radios, hotspots, gateways
M17	Open digital voice mode	M17 clients, radios, hotspots, gateways
NXDN	NXDN reflector-style connectivity	NXDN-capable clients or gateways
P25	P25 reflector-style connectivity	P25-capable clients or gateways
YSF	Yaesu System Fusion reflector-style connectivity	YSF radios, hotspots, gateways
VAFM	Analog FM linking through Vexillum clients	Software clients, audio interfaces, repeater/link nodes

Not every reflector provides every mode. Use the reflector’s public status page to confirm what is available.

D-Star

D-Star support may include D-Plus, DExtra, or DCS-style reflector behavior.

To connect, users typically need:

D-Star radio, hotspot, or gateway
Reflector hostname or IP address
Reflector type or protocol
Module
Proper callsign routing settings

Common default ports:

D-Star type	Default port
D-Plus	`20001`
DExtra	`30001`
DCS	`30051`

D-Star clients can be particular about naming, modules, and routing fields. Tiny fields, big consequences, because naturally.

DMR

DMR reflector-style connectivity may be available on a Vexillum reflector.

To connect, users typically need:

DMR radio, hotspot, or gateway
Reflector hostname or IP address
DMR port
Any ID, talkgroup, or routing settings required by the operator

Common default port:

Default DMR reflector behavior in Vexillum is as follows:

TG 7 for speaking on a module
TG 64001-64026 for switching modules (e.g. TG 64001 for module A, TG 64002 for module B, etc.)
TG 64000 to unlink from a module

These defaults may not be the same as other Vexillum deployments. Always follow the reflector operator’s published DMR instructions.

M17

M17 is an open digital voice mode.

To connect to an M17 service, users typically need:

M17-capable client, radio, hotspot, or gateway
Reflector hostname or IP address
M17 port
Module, if required
Correct callsign configuration

Common default port:

17000/udp

Use the port published by the reflector operator.

NXDN

NXDN reflector-style connectivity may be available when enabled by the operator.

To connect, users typically need:

NXDN-capable client, hotspot, or gateway
Reflector hostname or IP address
NXDN port
Any talkgroup or routing details required by the operator

Common default port:

P25

P25 reflector-style connectivity may be available when enabled by the operator.

To connect, users typically need:

P25-capable client, hotspot, or gateway
Reflector hostname or IP address
P25 port
Any talkgroup, NAC, or routing behavior required by the operator or client

Common default port:

YSF

YSF, or Yaesu System Fusion, is commonly used with Fusion radios, hotspots, and gateways.

To connect, users typically need:

YSF-capable radio, hotspot, or gateway
Reflector hostname or IP address
YSF port
Correct reflector selection in the client or hotspot software

Common default port:

42000/udp

VAFM

VAFM is Vexillum’s analog FM linking mode.

Unlike the digital voice modes, VAFM is intended for analog audio clients, link radios, repeater interfaces, and software clients that encode audio using Opus and connect to the Vexillum reflector.

To connect, users typically need:

VAFM-compatible client
Reflector hostname or IP address
UDP or TCP transport
VAFM port
Callsign
Microphone or radio audio input
Speaker or radio audio output
Optional shared passphrase, if required

Common default ports:

Transport	Default port
VAFM UDP	`43000`
VAFM TCP	`43000`

VAFM uses Opus audio internally. Most users should not need to configure codec details unless they are developing or debugging a client.

Published settings win

The default ports listed here are common defaults for Vexillum, not universal law.

The reflector operator may use different ports, hostnames, modules, rooms, or access rules. Always use the settings published for the specific reflector you are connecting to.

When the documentation and the operator disagree, assume the operator’s live configuration wins. Documentation ages like milk unless someone remembers to update it.