how to run radio automation software on raspberry pi

I had already run into this before, as it seems it doesn’t compile unless it has a later version of the ax25 stack compiled from source. Part of this app, when you run the make script, will create wl2kserial and wl2ktelnet, but not wl2kax25. I was initially trying to get this working because I wanted to run paclink-unix for Winlink email. docker run -it -privileged -v /dev/ttyAMA0:/dev/ttyAMA0 rpi-paclink Or, if you made it a module, that the module is loaded?Īlternatively, starting with –privileged. …When trying kissattach in the container, it gives: kissattach: Error setting line discipline: TIOCSETD: Operation not permittedĪre you sure you have enabled MKISS support in the kernel If you expose the serial port on the Raspberry Pi to the Container running paclink-unix: docker run -it -device=/dev/ttyAMA0 rpi-paclink I could not get ax25 to work self-contained in its own Docker container, as I ran into issues either accessing my serial device connected to my TNC Pi from inside the container and/or creating an ax0 interface when running kissattach.

Skip to the end if you just want to find out how to build and run the completed Docker containers.

I did eventually did get this working, building ax25 from source and using Pat, but it took me down a rabbit hole for several hours. Since the steps are well documented, I wondered if they could be captured in a Dockerfile to automate building a self-contained and ready-to-run Docker container.

Installing and configuring ax25 for the Raspberry Pi and Winlink clients that use ax25 like paclink-unix or Pat can be done and work well, but the steps, as, for example, documented in this comprehensive guide for building and installing paclink-unix that span several pages of instructions, can be daunting even for those more familiar with building and installing apps from source on Linux. Running Packet Radio apps in a Docker container on a Raspberry Pi? 'Are you mad,' I hear you ask? Isn’t it hard enough to get ax25 and Packet Radio up and running on the Pi anyway? Having done this a few times already, this was my thinking, and I had the crazy idea that encapsulating most of the config and setup in Dockerfiles to build preconfigured containers might be an idea worth exploring.

How to run radio automation software on raspberry pi