- 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.
- If you expose the serial port on the Raspberry Pi to the Container running paclink-unix: …When trying kissattach in the container, it gives: I was initially trying to get this working because I wanted to run paclink-unix for Winlink email.
- My TNC-Pi board connected to my Raspberry Pi is available on my serial device as /dev/ttyAMA0, so I start up my ax0 port like so: Next, run the container as a daemon, share the host networking, and expose port 8080 so we can access the Pat web app: Now let’s fire up the web app: Looks good!
- You can configure this yourself before creating the rpi-wl-pat image: Remember, the Pat web app that we’re interacting with here is running in a Docker container, on a Raspberry Pi.
- To send my email over RF to the Winlink gateway, click Action, then Connect: In the Pat status window, we now see a log of the Packet exchange between my station and AG6QO-10 via BERR37: A few seconds later, the email arrives in my Gmail inbox: If I reply to the email in Gmail, it will go back over the Winlink network, and be waiting for me when I connect to the Winlink gateway again over RF.
@craigbrownphd: “Packet Radio, Docker, and Raspberry Pi #IoT #Cloud #BigData” open tweet »