KISS TNC
Expose graywolf as a KISS terminal node controller
The KISS (Keep It Simple, Stupid) interface lets third-party packet software — such as Xastir, YAAC, pinpoint, or aprx — use graywolf as their TNC. Graywolf supports multiple simultaneous KISS interfaces over TCP, serial, or Bluetooth.
Interface Types
| Type | Description | Use Case |
|---|---|---|
| TCP (server) | Graywolf listens on a TCP port; clients dial in | Most APRS software (Xastir, YAAC, pinpoint, aprx, etc.) |
| TCP Client | Graywolf dials out to a remote KISS server and reconnects automatically | Bridging to a remote TNC, a LoRa modem, or another graywolf. See Remote KISS TNC. |
| Serial | Virtual serial port | Legacy software expecting a serial TNC |
| Bluetooth | Bluetooth serial profile | Mobile APRS apps (APRSdroid, etc.) |
Mode
Each KISS interface runs in one of two modes. The Mode column on the KISS Interfaces page shows you which.
| Modem | The KISS interface rides on top of a modem-backed channel. Frames you send through KISS get modulated and transmitted on RF; frames heard on the air get handed back to the KISS client. |
| TNC | The interface is the radio link — KISS frames are forwarded to and from an external TNC, a LoRa modem, or another graywolf over TCP Client. The channel itself is KISS-TNC-only (no software modem). |
Interface Settings
| Field | Default | Description |
|---|---|---|
name |
— | Display name for this interface |
type |
— | tcp, serial, or bluetooth |
listen_addr |
— | Listen address for TCP (e.g., 0.0.0.0:6700) |
device |
— | Device path for serial/Bluetooth |
baud_rate |
9600 |
Baud rate for serial interfaces |
channel |
1 |
Default radio channel for this interface |
broadcast |
true |
Fan out received packets to all connected clients |
enabled |
true |
Interface active/inactive |
TCP Setup
A TCP KISS interface is the most common setup. Configure it to listen
on a port and point your APRS software at host:port
with KISS protocol selected.
Port 6700 is the conventional KISS-over-TCP port used by most APRS software. If your APRS application asks for a “KISS TNC host”, point it at graywolf’s IP and this port.
Multi-Port KISS
The KISS protocol supports multiple “ports” (0–15) within a single connection. Each KISS port maps to a graywolf radio channel. Clients can send and receive on different channels through one TCP connection.
RX Broadcast
When broadcast is enabled, all packets received on the
interface’s channel are forwarded to every connected KISS client.
Disable this if you want a write-only interface where clients can
transmit but don’t receive.