By TA4OHN ·

Direwolf APRS Setup: A Practical Software TNC Guide

Direwolf is the program most APRS operators reach for when they want to turn a computer and a radio into a working station. It is a free software TNC and APRS engine by John Langner, WB2OSZ. It listens to the radio's audio through a sound card and decodes 1200 baud AFSK (and 9600 baud) packets, it can generate packets and key the transmitter, and it speaks the standard KISS and AGW protocols so that any APRS client on your network can use it as a modem.

This guide covers what you need to run it for APRS on a computer or Raspberry Pi: the audio interface, PTT, a minimal configuration, a first test, connecting client software, and the failures everyone meets. If your goal is specifically a receive-only gateway that uploads to the internet, the iGate setup guide already has a Direwolf walkthrough, and this page deliberately does not repeat it.

New to the idea of a TNC? Packet radio explained covers the background, and the AX.25 guide shows what Direwolf is encoding and decoding.

What Direwolf does

Direwolf bundles several functions that used to be separate devices:

It runs on Linux (including Raspberry Pi OS), Windows and macOS. On Debian-based systems sudo apt install direwolf is the quickest start; on Windows and for the latest version, see the project's releases page on GitHub.

What you need

The audio interface

Direwolf needs an audio path between the radio and the computer, and, for transmitting, a way to key the radio. The common options:

The radio

Any FM radio on the APRS frequency works. For 1200 baud, the speaker or headset jack and the microphone input are enough for a start. A radio with a 9600 baud data port is preferable if you need 9600 baud. Use the correct frequency for your region: 144.390 MHz in the Americas, 144.800 MHz in Europe and Africa (see frequencies by country).

PTT methods

Direwolf offers several ways to key the transmitter. Pick one:

Method Typical use Config line
Serial RTS (or DTR) Interfaces with a serial port, such as Digirig PTT /dev/ttyUSB0 RTS
GPIO pin Raspberry Pi wired to a transistor or optocoupler PTT GPIO 25
CM108 GPIO USB sound card with a PTT pin PTT CM108
Hamlib rigctld Rig control by CAT PTT RIG 2 localhost:4532
VOX SignaLink and other VOX interfaces no PTT line

Add a leading minus to invert the polarity, for example PTT /dev/ttyUSB0 -RTS. The exact syntax for your version is in the Direwolf User Guide.

A minimal direwolf.conf

Direwolf reads a plain text file. The one below is a transmit-capable station with a beacon, an RX iGate function and both client ports. Replace the callsign, passcode and position with your own; the iGate-specific lines follow the same syntax as in the iGate setup guide.

ADEVICE plughw:1,0
CHANNEL 0
MYCALL N0CALL-9
MODEM 1200
PTT /dev/ttyUSB0 RTS

KISSPORT 8001
AGWPORT 8000

PBEACON delay=1 every=30 symbol="/-" \
        lat=40^30.00N long=032^53.00E \
        comment="aprs.world test station" via=WIDE1-1,WIDE2-1

IGSERVER rotate.aprs2.net
IGLOGIN N0CALL-9 12345

What the lines mean:

To upload only what you hear and never transmit, skip PTT and use sendto=IG on the beacon so that your own beacon only goes to the internet, as in the iGate guide.

If you want a mobile tracker rather than a fixed beacon, Direwolf can read a GPS through gpsd and send TBEACON position reports with SmartBeaconing-style timing; see the User Guide's section on tracker beacons and our SmartBeaconing guide.

Run it and test it

Start Direwolf in a terminal with your configuration:

direwolf -c direwolf.conf -t 0

-t 0 turns off the coloured text output, which is useful when a terminal or log file does not render colours. You can omit it for an ordinary terminal.

Do the tests in this order, because each one proves one part of the chain:

  1. Receive. Tune the radio to the APRS frequency and open the squelch just enough to quiet the radio. You should see a line for each decoded packet, with the sender, the path and the payload, followed by an audio level = ... line. If nothing appears on a busy frequency, fix receive before anything else.
  2. Known signal. To test the decoder without relying on the air, run atest on a recorded WAV file. The bundled tools and the public TNC test recordings let you compare decode counts with other software.
  3. Transmit. With a PBEACON in the configuration, Direwolf transmits after the delay. Start with a dummy load or a low-power setting and key into a second receiver nearby if you can.
  4. On the map. Once you are heard by a digipeater or iGate, open aprs.world and search for your callsign, or go straight to aprs.world/station/N0CALL-9 using your own callsign. If you only uploaded through IGSERVER, you appear from the internet side.

Connecting client software

Direwolf is the TNC; the user interface is another program. These connect over the network sockets Direwolf exposes:

Xastir, YAAC, APRSIS32 and PinPoint APRS can all use Direwolf this way; in each, create a new TNC or network interface and choose the KISS TCP or AGW type that the program lists. The addresses to use are localhost when the client is on the same machine, or the machine's LAN address when it is not. Our APRS software overview compares these clients.

One caution: the KISS TCP and AGW ports have no password. Any device that can reach them can make your station transmit. Keep them on a trusted local network and do not forward them through your router to the internet.

Common failure modes

Frequently asked questions

What is Direwolf?

Direwolf is a free, open-source software TNC and APRS engine written by John Langner, WB2OSZ. It turns a computer's sound card into a packet modem for 1200 and 9600 baud, and it can also act as a digipeater, an iGate and a KISS or AGW server for other software. It runs on Linux, Windows, macOS and Raspberry Pi.

Which port do APRS clients use to connect to Direwolf?

Direwolf serves KISS over TCP on port 8001 by default and the AGW protocol on port 8000. Set KISSPORT 8001 and AGWPORT 8000 in direwolf.conf, then point your client at the computer running Direwolf on the port that matches the interface type the client supports.

Do I need a PTT line for Direwolf?

Only if you transmit. A receive-only setup, such as an RX iGate, needs no PTT. For transmitting you need a way to key the radio: a serial RTS or DTR line, a GPIO pin on a Raspberry Pi, a CM108 USB sound card GPIO pin, hamlib rigctld, or VOX on an interface such as the SignaLink.

Why does Direwolf decode few packets?

The usual cause is the audio level. Too low and weak packets are missed, too high and the signal clips. Direwolf prints an audio level with every decoded packet and warns when the input is too high; adjust the radio volume or the sound card capture level until typical stations show a mid-range level. Also check that the radio is on the right APRS frequency.

Can Direwolf be an iGate and a digipeater at the same time?

Yes. Direwolf can decode packets, upload them to APRS-IS as an iGate, and repeat packets on the air as a digipeater, all from one configuration. For a first build, start with a receive-only iGate and add transmitting later.

Does Direwolf work with a Raspberry Pi?

Yes, and it is the most common home iGate platform. A Raspberry Pi has no audio input of its own, so you need a USB sound card or an interface such as the Digirig for the radio audio, or an SDR for receive-only use.

Further reading