🍓 Raspberry Pi — headless (32-bit ARM)
🐧 Headless Debian Package (armhf)
k2k-headless_0.11.38_armhf.deb — 692 KB, 2 MB installed, no GTK/WebKit
Download
📦 Source (rebuild it yourself)
k2k-headless_0.11.38-source.tar.gz — 3.2 MB · includes the armhf build script, systemd unit and packaging README
Download
This is the same app built without a window: no GTK, no WebKitGTK, so it installs in seconds
instead of pulling ~350 MB of GUI libraries. It serves the normal K2K client over HTTP and you drive it
from a browser on any machine on the LAN — ideal for a Raspberry Pi sitting next to the TNC.
Only libc6 and
libgcc-s1 are required.
📋 What’s new in the headless build v0.11.38 — NET/ROM frames decode as NET/ROM
- Fixed: every NET/ROM frame printed a fake routing table. A NET/ROM data frame — a BBS banner, a message list, a connect or a disconnect — appeared in the monitor as
NET/ROM Routing: followed by rows of noise, because the routing-table parser was run on frames that are not routing broadcasts.
- NET/ROM data now reads as data: originating and destination node, circuit index/id, TTL, TX/RX sequence, the more-follows / NAK flags, and the text payload with real line breaks.
- Circuit control frames are named — connect request (with proposed window and originating user), connect acknowledge, refused connect, disconnect request, disconnect acknowledge.
- Routing broadcasts are unchanged, and only PID
0xCF is treated as NET/ROM, so other frames keep their real PID.
📋 What’s new in the headless build v0.11.37 — several browser tabs share one TNC
- Fixed: only the newest tab could transmit. Every tab used to dial its own TNC connection, and connecting to the same address tears down the existing one — so opening a second tab killed the first tab’s connection and sending from it produced Connection not found above the message area. (It also dropped and re-made the radio link each time a tab loaded.)
- One connection, every tab. A tab that loads while the server is already connected to the TNC now reuses that connection instead of redialling, and says so in the transcript. Any tab can send; the link stays up.
- Desktop app unchanged — it has its own backend, so there is nothing to share. The installers above are v0.11.37 too.
Install
wget https://map.kk6sen.com/downloads/k2k-headless_0.11.38_armhf.deb
sudo apt install ./k2k-headless_0.11.38_armhf.deb
Run
k2k-headless # serves on 0.0.0.0:8080
k2k-headless --port 8081 # different port
k2k-headless --bind 127.0.0.1 # this machine only
Then open http://<pi-address>:8080/ in a browser.
In the connect bar, point it at Direwolf on the same Pi: 127.0.0.1 port 8001 (KISS).
Run it as a service (starts with the Pi)
sudo systemctl enable --now k2k-headless
systemctl status k2k-headless
journalctl -u k2k-headless -f # live log
sudo nano /lib/systemd/system/k2k-headless.service # change user or port
Where it keeps its data
~/.local/share/K2KDesktop/settings.json
~/.local/share/K2KDesktop/pbbs_data.json
~/.local/share/K2KDesktop/logs/YYMMDD_<kind>.log
Same files and lay-out as the desktop app, so the message board, settings and logs are shared between the two.
Local network only — there is no password and no TLS; use --bind 127.0.0.1 to keep it on the Pi itself.