Connecting to a Reflector
This page explains the general process for connecting to a Vexillum-powered reflector.
The exact settings depend on the mode you are using. M17, D-Star, DMR, NXDN, P25, YSF, and VAFM all have their own client behavior and configuration conventions, because apparently one radio hobby was not enough to contain all possible setup screens.
Before you start
Section titled “Before you start”Collect the connection details for the reflector.
You may need:
| Setting | Description |
|---|---|
| Hostname | The DNS name or IP address of the reflector |
| Port | The network port for the mode you are using |
| Mode | M17, D-Star, DMR, NXDN, P25, YSF, or VAFM |
| Module or room | Mode-specific routing target, if used |
| Callsign | Your amateur radio callsign |
| Passphrase | Optional shared access passphrase, if required |
| Client type | Radio, hotspot, gateway, software client, or VAFM client |
Whatever the operator publishes, a status page, dashboard, or plain documentation, should provide the most accurate connection information.
Step 1: Choose a mode
Section titled “Step 1: Choose a mode”Choose the mode supported by your radio, hotspot, gateway, or client.
A Vexillum reflector may support:
- D-Star
- DMR
- M17
- NXDN
- P25
- YSF
- VAFM
Not every reflector enables every mode. If a mode is not listed in the operator’s published connection details, do not assume it is available.
Step 2: Confirm the hostname
Section titled “Step 2: Confirm the hostname”Use the hostname provided by the reflector operator.
Example:
Avoid using old IP addresses or connection details from screenshots, chat messages, or ancient forum posts unless the operator confirms they are still valid. Radio software already has enough ghosts.
Step 3: Confirm the port
Section titled “Step 3: Confirm the port”Each mode usually has its own port.
Common Vexillum defaults are:
| Mode or service | Default port |
|---|---|
| D-Star DExtra | 30001 |
| DMR | 62031 |
| M17 | 17000 |
| NXDN | 41400 |
| P25 | 41000 |
| YSF | 42000 |
| VAFM UDP | 43000 |
| VAFM TCP | 43000 |
The operator may use different ports. Always follow the published connection details for the reflector you are using.
Step 4: Configure your callsign
Section titled “Step 4: Configure your callsign”Set your callsign in your client, radio, hotspot, or gateway.
Use your valid amateur radio callsign. Some modes are sensitive to callsign formatting, spacing, suffixes, or module conventions.
For VAFM, callsigns are sent as fixed-width fields by the client. Most users should only need to enter their normal callsign in the client configuration.
Step 5: Configure mode-specific settings
Section titled “Step 5: Configure mode-specific settings”Depending on the mode, you may need additional settings.
Examples:
| Mode | Possible settings |
|---|---|
| D-Star | Reflector type, module, callsign routing |
| DMR | Reflector address, port, optional passphrase, ID or talkgroup behavior |
| M17 | Reflector address, module |
| NXDN | Reflector address, port, talkgroup or routing settings |
| P25 | Reflector address, port, talkgroup or NAC-related settings |
| YSF | Reflector address and port |
| VAFM | Transport, hostname, port, callsign, audio device, optional passphrase |
Check the mode-specific documentation for your client or radio.
Step 6: Connect
Section titled “Step 6: Connect”Start the client connection.
If the reflector provides a status page or dashboard, check whether the service is online before troubleshooting your own setup.
For a first test:
- Connect.
- Wait a few seconds.
- Confirm the client shows connected state.
- Listen before transmitting.
- Make a short test transmission if appropriate.
Example test phrase:
Replace the callsign with your own, unless you are trying to make logging exciting for the wrong person.
Step 7: Listen before transmitting
Section titled “Step 7: Listen before transmitting”Before transmitting, listen for active traffic.
Good practice:
- Wait for an idle period.
- Leave a pause between overs.
- Keep initial test transmissions short.
- Identify clearly.
- Avoid repeated kerchunking or rapid reconnect tests.
Remember that a reflector may connect users across wide areas. Your short test may be heard by more people than expected.
Step 8: Disconnect cleanly
Section titled “Step 8: Disconnect cleanly”When finished, disconnect through your client or stop the radio/hotspot connection cleanly.
For VAFM, a clean disconnect allows the client to send a session close message to the server.
For other modes, clean shutdown behavior depends on the client, hotspot, or gateway software.
Connection checklist
Section titled “Connection checklist”Before reporting a problem, confirm:
- The reflector is online.
- The mode is enabled.
- The hostname is correct.
- The port is correct.
- Your callsign is configured.
- Your client supports the selected mode.
- Any passphrase or access setting is correct.
- Your firewall or network allows the connection.
- Your radio, hotspot, or client has been restarted after changes.
- You are not using stale connection details.
When to contact the operator
Section titled “When to contact the operator”Contact the reflector operator if:
- The published status page or dashboard shows the mode online but no users can connect.
- Multiple users report the same issue.
- Your client receives a clear authentication or access error.
- Published connection details appear incorrect.
- The reflector has been offline longer than expected.
- You need access details that are not published.
Include useful details. Operators are not clairvoyant, no matter how often users attempt to use them that way.