These are my lab notes from building VEXJET, my own Vexillum server at vex.n6jet.com, between 2 and 11 November 2026. They follow the order I did things in, and they include every problem I ran into and how it was solved. If you want to know what Vexillum is first, read Vexillum (VEX) Reflector Explained.
At a glance
Read this first
Vexillum is beta software. Flags, forms and behavior are still changing from one release to the next. Everything here was true for v0.2.0b in November 2026. Newer releases may work differently, so check the docs at vexdv.io before you copy anything. Never put real passwords on a web page or in shared notes.
Most of my problems came from sharing one server with other reflectors. If Vexillum has a server to itself, you can skip much of this section.
vex.n6jet.com with an A record at my DNS provider pointing to the IP address VEXJET would use. Do this early, because DNS and the web certificate both need it.0.0.0.0 holds that port on all addresses. On my server the old P25Reflector held 41000 on all addresses, and xlxd and urfd held 30001, 41400 and 17000 on their own addresses.127.0.0.1. Reach the admin page through an SSH tunnel. Only the public API goes on the web, through your web server.What VEXJET ended up using:
| Mode | Vexillum default | VEXJET | Why it changed |
|---|---|---|---|
| DMR | 62030 | 62031 | 62030 is used by xlxd and urfd |
| M17 | 17000 | 17002 | 17000 is urfd, 17001 is mrefd |
| YSF | 42000 | 42000 | Free on VEXJET's own address |
| NXDN | 41400 | 41400 | Free on VEXJET's own address |
| P25 | 41000 | 41100 | Took over the address of a retired P25 reflector |
| D-STAR (DExtra) | 30001 | 30001 | Free on VEXJET's own address |
| Admin, metrics, public API | 8080, 9090, 8081 | 8080, 9090, 8085 | 8081 was already used by another program |
Releases are on the author's own code server, linked from vexdv.io Downloads. There is no GitHub mirror. When the code server was down for a day, I simply had to wait. I emailed the author, and it was back the next day.
vexillum-linux-amd64 and SHA256SUMS.txt. For v0.2.0b the file is 21,020,834 bytes.sha256sum -c against the SUMS file.vexillum, and a folder /opt/vexillum owned by it./opt/vexillum/vexillum, owned by root, mode 755. It has only two flags: -config and -version.The config file is small. Mine, with comments removed:
[runtime] name = "VEX-JET" [logging] level = "info" format = "text" [database] url = "sqlite://vexillum.db" [admin] enabled = true listen = "127.0.0.1:8080" [metrics] enabled = true listen = "127.0.0.1:9090" [public_api] enabled = true listen = "127.0.0.1:8085" rate_limit_per_minute = 120 rate_limit_burst = 20
Lessons
/opt/vexillum (WorkingDirectory), and so must every command-line tool you run later.I wrote a systemd unit that runs Vexillum as the vexillum user with the usual hardening (NoNewPrivileges, ProtectSystem=strict, ProtectHome). Two extra tricks were worth it on a shared server.
Vexillum may try to open default ports that other reflectors already hold. systemd can block that. I allow only the ports VEXJET should use and deny everything else:
SocketBindAllow=tcp:8080 SocketBindAllow=tcp:9090 SocketBindAllow=tcp:8085 SocketBindAllow=udp:62031 SocketBindAllow=udp:17002 SocketBindAllow=udp:42000 SocketBindAllow=udp:41400 SocketBindAllow=udp:41100 SocketBindAllow=udp:30001 SocketBindDeny=any
Put one port on each line. On systemd 255 a space-separated list on one line was silently ignored. Each time you add a mode, add its port here, open it in the firewall for that IP address only, and restart.
The M17 form has no address field, so Vexillum listens for M17 on every IP address of the server. Packets came in on VEXJET's address, but the replies went out from the server's main address, and hotspots behind a home router threw them away. Rewriting the reply address in the firewall did not work: the replies vanished. What did work was routing by user. Everything the vexillum user sends uses a routing table whose source address is VEXJET's IP:
ExecStartPre=+/usr/sbin/ip route replace default via <gateway> dev eth0 src <VEX IP> onlink table 172 ExecStartPre=+-/usr/sbin/ip rule del uidrange <vexillum uid>-<vexillum uid> priority 1000 table 172 ExecStartPre=+/usr/sbin/ip rule add uidrange <vexillum uid>-<vexillum uid> priority 1000 table 172
If your server has only one IP address, you do not need this.
VEX_ADMIN_BOOTSTRAP_PASSWORD. It must be at least 12 characters. My first try with a short one stopped the service with an error. I put it in a root-only file loaded with EnvironmentFile=- (the dash means "fine if the file is missing").http://127.0.0.1:8080/healthz on the server and the public liveness page on 8085.ssh -N -L 8080:127.0.0.1:8080 root@your-server, then browse to http://localhost:8080. Log in as admin and change the password right away.A fresh install starts with no instances at all. Nothing is created for you. You add each mode yourself.
Each mode is an "instance", created on the admin page. Before each one: add its port to the service lockdown, open the firewall, restart. Then create the instance and click Start. Once my first click on Start did nothing, and a second click worked.
| Mode | What I entered | Lessons |
|---|---|---|
| M17 | UDP 17002, designator JET, endpoint vex.n6jet.com:17002 | No address field: it listens on all addresses (see Trick 2). Modules A to Z. |
| DMR | Listen VEX IP:62031, talk TG 7, default module A, unlink 64000, status 65000 | Modules are reached as TG 64001 to 64026, then you talk on TG 7. The password is stored as plain text. VEXJET uses the open password passw0rd, like XLX and URF. I changed it in the database because the admin page had no field for it. |
| YSF | Listen VEX IP:42000, designator 95114, room name VEXJET | One room only, no DG-ID rooms. Use a 5-digit number as the designator, or it can never appear in hotspot host lists. There is no edit page for YSF instances in v0.2.0b, so changing the designator meant editing the database with the service stopped. |
| NXDN | Listen VEX IP:41400, TG 9512 | One room. Answers the standard NXDNGateway poll. |
| P25 | Listen 41100, TG 9512 | One room. Answers the standard P25Gateway poll. |
| D-STAR | DExtra VEX IP:30001, designator JET, modules A to Z | Only DExtra was offered in the form, not DPlus or DCS. A test link got an ACK right away. |
Lessons
vexillum.db.Vexillum has no dashboard of its own. It has a read-only public API (/api/public/v1/...) that dashboards and DVRef read. I added W0CHP's free vex-dashboard, built from source with Go, listening on 127.0.0.1:8090.
The key is to serve both from one https address. My Apache site for vex.n6jet.com sends the API paths to Vexillum and everything else to the dashboard:
ProxyPreserveHost On ProxyPass /api/public/ http://127.0.0.1:8085/api/public/ flushpackets=on ProxyPassReverse /api/public/ http://127.0.0.1:8085/api/public/ ProxyPass / http://127.0.0.1:8090/ ProxyPassReverse / http://127.0.0.1:8090/
flushpackets=on keeps the live event streams flowing. A free Let's Encrypt certificate covers the https side. Now https://vex.n6jet.com/ shows the dashboard and https://vex.n6jet.com/api/public/v1/liveness answers for DVRef.
The most common mistake
If your Dashboard URL points straight at the dashboard program's port (for example http://yourhost:8090), the API is not there. The dashboard answers "404 page not found", and DVRef shows "Vexillum liveness API returned an error: HTTP 404". Another VEX operator ran into exactly this in November 2026. Put both behind one https address as shown above.
The dashboard can show an About tab from a Markdown file (about.md, set with an environment variable). To change it, edit the file and restart the dashboard.
DVRef is the directory that hotspot host lists are built from. A VEX server is listed in two layers: one VEX Server record, then one instance under it for each mode.
Do not register instances twice
Lessons
VexDV (activity.vexdv.io) is the project's own live directory of VEX servers and stations. Joining is optional.
[activity.public] enabled = true display_name = "VEX-JET (N6JET, San Jose CA)"
/opt/vexillum as the service user, because the database path is relative:
cd /opt/vexillum && runuser -u vexillum -- ./vexillum publisher request -callsign YOURCALL -email you@example.com -config /opt/vexillum/vexillum.toml
publisher verify with it before it expires (24 hours).Check progress any time with publisher status.
Because VEX instances may not reach the hotspot host files, I add VEXJET to my hotspots by hand. On Pi-Star the custom host files live in /root/ (for example /root/DMR_Hosts.txt, /root/YSFHosts.txt, /root/M17Hosts.txt) and survive the nightly update. On WPSD use the Hosts File Editors. Step-by-step instructions with the exact lines are on Vexillum (VEX) Reflector Explained and How to Connect to N6JET Reflectors.
When you pick an alias for a custom host, search the full host lists first. My first D-STAR alias, XRFJET, turned out to be a real registered name (it belongs to XLXJET), and my gateway linked to the wrong reflector. I renamed it XRFVEX.
Bridges are small separate programs from the Vexillum project that link a VEX room to another network or another mode. VEXJET runs three:
| Bridge | Joins | Notes |
|---|---|---|
| vex-dmr-bridge | TGIF TG 95110 and VEXJET DMR module A | Logs into VEXJET like a repeater and into TGIF like a hotspot, with its own DMR ID and my TGIF hotspot password. |
| vex-dmr-ysf-bridge | DMR module A and YSF 95114 | Same voice codec on both sides, so no conversion. Uses the RadioID database to show callsigns. |
| vex-nxdn-ysf-bridge | NXDN 9512 and YSF 95114 | Reaches DMR through the YSF bridge. |
Which bridge version to build
The newest bridge code uses a new "bridgelink" protocol with a token. Vexillum v0.2.0b does not support it: nothing listens on its port, and no token appears when you designate a bridge. The older versions from before bridgelink are still in the public code history, and they work with v0.2.0b. Build them from source with Go 1.25 or newer:
git clone https://repo.kc1awv.net/Vexillum/vex-dmr-bridge.git cd vex-dmr-bridge git checkout 28c1bf0 go build
The versions VEXJET uses: vex-dmr-bridge 28c1bf0, vex-dmr-ysf-bridge 05bb745, vex-nxdn-ysf-bridge d8f652c.
Lessons
-vex-description text can be at most 19 bytes. 20 failed.PartOf=vexillum.service (restart together) and ExecStartPre=/bin/sleep 8 (wait for Vexillum's listeners).Vexillum has no bridge for M17, P25 or D-STAR. To put those on module A with DMR, I built a converter from DVSwitch parts, the same pattern as my older "N6JET Six Link". Each mode gets a "leg" that turns its digital voice into plain audio, and a small relay program passes the audio between the legs so each leg hears the others but never itself. The relay is explained on The Multimode USRP Fanout Bridge.
Options=Module=B.Lessons
gatewayDmrId must be different from repeaterID.D-STAR uses an older AMBE codec that needs a hardware chip. I used two spare DVstick 30s plugged into a small Linux box at home, linked to the server over Tailscale. Four problems had to be solved:
After that, a 3-second test tone sent into the D-STAR leg came out as 156 D-STAR voice frames on VEXJET module A, in real time. The same worked on module B.
/opt/vexillum, because the database path is relative.SocketBindAllow line.PartOf= and a short start delay.Most of this page comes from one origin, my own build, checked against the project's documentation. Your server will be different. Test as you go.
A noncommercial hobby reference compiled by N6JET, gathered from hands-on work and public sources, and shared freely for anyone interested in amateur digital voice. Version 1.2, 11 November 2026.