How to Run aprsc APRS-IS Server on FreeBSD

9M2PJU — Sat, 31 May 2025 07:06:16 +0000

Running an APRS-IS server with aprsc on FreeBSD is a powerful way to contribute to the APRS network or run your own regional server. Below I’ll walk you through a solid example configuration based on a working aprsc.conf file with explanations for each section.

Understanding the aprsc.conf File

Here’s a typical aprsc.conf you might use — based on your shared config:

# Unique server ID for this APRS server
ServerId   9M2PJU

# Passcode for this server ID, assigned via the APRS passcode generator
PassCode   12345

# Administrator contact info
MyAdmin    "Piju, 9M2PJU"
MyEmail    9m2pju@hamradio.my

### Directories
# Directory to store persistent data, such as state and logs
RunDir /usr/local/piju/aprsc/data

# Log rotation: max file size (MB) and number of files
LogRotate 100 50

### Intervals and timeouts
# How long to wait for upstream server data before switching
UpstreamTimeout 5s

# How long to wait before disconnecting a client due to inactivity
ClientTimeout 48h

### TCP/UDP listeners
# Listen on both IPv4 and IPv6 for various port types

Listen "Full feed" fullfeed tcp :: 10152
Listen ""          fullfeed udp :: 10152
Listen "Full feed" fullfeed tcp 0.0.0.0 10152
Listen ""          fullfeed udp 0.0.0.0 10152

Listen "Client-Defined Filters" igate tcp :: 14580
Listen ""                  igate udp :: 14580
Listen "Client-Defined Filters" igate tcp 0.0.0.0 14580
Listen ""                  igate udp 0.0.0.0 14580

Listen "UDP submit" udpsubmit udp :: 8080

### Uplink configuration
# Connect as a full feed to the APRS core network
Uplink "Core rotate" full tcp rotate.aprs.net 10152

### HTTP server for status and uploads
HTTPStatus 0.0.0.0 14501
HTTPUpload 0.0.0.0 8080
HTTPStatusOptions ShowEmail=1

Key Configuration Notes

ServerId & PassCode

ServerId is your unique server identifier visible on APRS networks. Use your callsign or a distinct tag.
PassCode must match your ServerId and be generated from a trusted APRS passcode generator (e.g., https://pass.hamradio.my).

Directories and Logs

RunDir points to where persistent state files and caches are stored — ensure this directory exists and is writable by the aprsc user.
LogRotate helps keep logs manageable, rotating files after hitting size limits.

Listeners

You must listen on TCP and UDP ports on both IPv4 (0.0.0.0) and IPv6 (::).
The fullfeed ports (10152) provide a full stream of APRS data (filtered for duplicates).
The igate ports (14580) are for clients like digipeaters, iGates, or APRS software that connect with filters they define.
udpsubmit on port 8080 allows lightweight position uploads over UDP.

Uplink

Your server connects upstream to the main APRS backbone via rotate.aprs.net on port 10152 with a full feed.
The full keyword means your server both receives and forwards data upstream.

HTTP Server

HTTPStatus provides a web interface with connection stats and server status on port 14501.
HTTPUpload allows users to upload position data via HTTP POST on port 8080.
ShowEmail=1 optionally shows the admin email on the status page.

Preparing FreeBSD for aprsc

Create directories:

mkdir -p /usr/local/piju/aprsc/data
chown -R aprscuser:wheel /usr/local/piju/aprsc

Replace aprscuser with the user running aprsc.

Firewall rules:
Allow inbound TCP and UDP on ports 10152, 14580, 8080, and 14501.
Run aprsc:

/usr/local/sbin/aprsc -f /path/to/aprsc.conf

Check logs for errors in /var/log or wherever configured.

Final Tips

Always generate your PassCode for your ServerId; don’t guess it.
For production, run aprsc as a dedicated user with limited permissions.
Monitor uptime and client connections via the HTTPStatus web page.
Consider automatic service management with an rc.d script for FreeBSD.

Summary

This config example is verified for current aprsc versions and is fully compatible with FreeBSD’s networking model. You have IPv4/IPv6 dual-stack listeners, client and uplink connections, and HTTP monitoring — all essentials for a robust APRS-IS server.

The post How to Run aprsc APRS-IS Server on FreeBSD appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

Introducing ARDOPC: A Powerful Command-Line Tool for ARDOP Communication

9M2PJU — Sun, 27 Apr 2025 21:10:49 +0000

If you’re a radio amateur or an enthusiast involved in digital communication, you’re probably familiar with ARDOP (Amateur Radio Digital Operating Protocol). ARDOPC, a command-line version of ARDOP_WIN, brings a new level of flexibility and control to your digital communication setup. Developed by John Wiseman (G8BPQ), ARDOPC is a versatile software that supports both TCP and Serial host interfaces, making it ideal for users working with ARDOP and other modes.

Key Features of ARDOPC:

TCP and Serial Host Support
ARDOPC offers seamless communication via TCP (using two TCP ports) or Serial (via a Virtual COM port) to connect with your host system. For serial communication, ARDOPC can emulate an SCS Dragon controller, allowing software like Winlink Express and Airmail, which doesn’t support ARDOP directly, to operate with ARDOP.
Easy Configuration for Hosts
When you run ARDOPC without parameters, it defaults to listen on TCP port 8515, with Linux using the virtual sound device ARDOP and Windows selecting the first available capture and playback device. Custom configurations can easily be set by specifying parameters for port and devices.
Sample Rate Conversion for Linux Users
On Linux, sound cards might not support the 12000 samples/second rate that ARDOP requires. ARDOPC handles this issue by allowing you to enable sample rate conversion, ensuring compatibility with a wide range of sound devices.
Versatile PTT (Push-To-Talk) Options
ARDOPC offers flexible PTT control methods, including sending PTT commands to the host (useful when running multiple modes like ARDOP and WINMOR), or controlling PTT via hardware (such as CAT control) or GPIO pins (on Raspberry Pi). The program supports various parameters for PTT, allowing for customization to suit your setup.
Logging and Debugging
ARDOPC generates a debug log and outputs detailed information to the console, making it easy for users to troubleshoot and optimize their ARDOP communication setup.
Windows and Linux Compatibility
Whether you’re using Windows or Linux, ARDOPC ensures smooth operation with both operating systems. It also supports virtual COM ports, making it compatible with a variety of radio equipment and digital modes.

How to Get Started:

To start using ARDOPC, simply download the latest version for your system:

Virtual COM Port Installation:

For Windows users, ARDOPC can integrate with BPQ32’s Virtual COM Port driver, allowing for easy setup and connection. Alternatively, you can download the necessary files from CAT7200.zip.

Experimental Graphical Front End: ARDOP_GUI

For users who prefer a graphical interface, John Wiseman has developed ARDOP_GUI, an experimental front-end for ARDOPC. This tool offers a similar look and feel to ARDOP_WIN.exe, complete with constellation, waterfall, and spectrum displays, along with various status indicators. It supports both Windows and Linux platforms and allows for easier monitoring of ARDOP communication.

Why Choose ARDOPC?

Whether you’re a seasoned digital mode operator or just getting started with ARDOP, ARDOPC provides a reliable and easy-to-use solution for your communication needs. With its flexibility, ease of use, and robust support for both TCP and serial connections, ARDOPC is an essential tool for anyone interested in ARDOP communication.

Start using ARDOPC today and enhance your digital communication capabilities. Check out the software, try the setup, and explore its potential for your own projects!

Visit https://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html

The post Introducing ARDOPC: A Powerful Command-Line Tool for ARDOP Communication appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

TCP - Hamradio.my