r/broadcastengineering • u/Efficient_Papaya_559 • 10h ago
Radio VPN – An open-source VPN solution for FM broadcast infrastructure, with automated backup and disaster recovery
Hi everyone,
I'm a broadcast technician working at an FM radio station in France, and I'd like to share an open-source project I've been developing: Radio VPN.
The idea is simple: improve the reliability and maintainability of network connections between radio studios, remote transmitter sites, and other broadcast equipment.
Many FM stations rely on IP networks to transport audio and exchange data between their studios and transmitter sites. VPN tunnels can provide a useful private network infrastructure for these connections.
Radio VPN is based on OpenVPN Community Edition, running on a minimal Debian 13 server, with a Web interface for managing clients and certificates.
Flexible deployment
Depending on the station's network architecture, the VPN server can be hosted:
- On a small cloud VPS, acting as a central connection point between remote sites.
- Directly at the radio studios, when the local network configuration allows it.
A basic VPS costing around €5 per month can be sufficient for some installations. Of course, actual requirements depend on the number of connected sites, bandwidth, audio streams and overall network architecture.
The objective is not to impose one particular network topology, but to provide a flexible solution that can be adapted to each radio station.
Automated deployment and disaster recovery
Installing OpenVPN is not particularly difficult. What interested me was simplifying its deployment, administration and, especially, recovery after a server failure.
The project includes three complementary tools:
- radio-vpn: automated OpenVPN server deployment, including a Web management interface and security configuration.
- radio-vpn-backup: automated backup of the server configuration, certificates and VPN data.
- radio-vpn-restore: reconstruction and restoration of a failed server, preserving existing client certificates and VPN identities.
This last point is particularly important in broadcasting: after a VPS failure, having to regenerate and redistribute VPN certificates to multiple remote transmitter sites can become a serious operational problem.
The goal is to simplify recovery and avoid unnecessary interventions at remote sites.
Technical approach
- Debian 13, without Docker.
- OpenVPN Community Edition.
- Web-based client and certificate management.
- Fixed VPN addresses for connected equipment.
- SSH key authentication and nftables firewall.
- Automated backup and restoration tools.
- Open-source, MIT license.
Radio VPN is not an audio codec or an audio transport protocol. It provides the network layer over which existing broadcast audio transport systems and other IP services can communicate.
It is also not intended to replace redundant network connections or audio failover mechanisms. Those remain important parts of reliable FM broadcasting.
GitHub
The project, installation instructions and links to the backup/restore tools are available here:
https://github.com/SmallTech2/radio-vpn
The documentation is currently in French, but the code is publicly available.
I'm sharing this in case it can be useful to other FM broadcast engineers, particularly those managing multiple transmitter sites with limited budgets.
I'd also be interested in hearing how other stations handle VPN connectivity, remote site management and disaster recovery.
Feedback and technical suggestions are welcome!