Guides
Join the conversation in just a few minutes.
From the first connection to your own server: these guides walk you through setting up the client, the Android app, your own server, Crosslink and the gateway.
- Desktop client
- Windows 7 & XP
- Android
- Your own server
- Existing systems
- Crosslink
- Gateway
- Troubleshooting
The screenshots show demo data; input fields and personal details have been redacted.
Desktop
Windows 10/11 and Linux.
The desktop client is the easiest way into FRN. You only need the right file, your access credentials and the server address of your network.
1. Download and start the client
Lade den Windows-Client, das Debian-Paket oder die Linux-Binary. Unter Windows startest du die EXE per Doppelklick. Unter Linux installierst du das .deb oder machst die Binary ausführbar.
2. Fill in the settings
- Call sign: your name or call sign on the network.
- Email: the address the server operator knows.
- Password: your password or a dynamic password.
- Server and port: the address of your FRN server.
- Network: the room you want to talk in.
With an open server without registration, a call sign and server are often enough. Ask the operator what details they require.
3. Show or hide the settings
The Debian client shows the settings on the left. Hide settings collapses the panel to the left; the participant list and chat then use the full window width. Show settings brings it back.
4. Save and connect
Click Save and then Connect. The other clients then appear in the participant list. If the list stays empty, check the server, port and network.
5. Talking with push-to-talk
Hold down the PTT button and speak. Releasing ends the transmission. Unlike a switch, the microphone does not stay open.
6. Chat and participants
Click a participant to send a private message. “To everyone” switches to a group call. New messages appear in the chat area.
7. Check the audio
Under Audio, select the correct input and output device. Use the test tone to check transmission and playback without speaking into the microphone. Level and mute help with feedback or transmission that is too quiet.
8. Administration with admin rights
Owner, Netzowner und Admins sehen den Bereich Administration. Dort bearbeitest du die Zugangsliste deines Netzes, setzt Sprechrechte, entfernst E-Mails und pflegst die Info-Nachricht beim Beitritt. Einfaches HTML wie <br>, <p> und <a href="mailto:..."> wird unterstützt.
Switching servers: recently used servers are listed in the server list. Switching also sets the port and network. If a server fails, the client automatically connects to the fallback server.
Windows 7 & XP
Setting up the native clients.
Both clients are single EXE files. They need no installation and no additional runtime. Setup differs in only a few points.
Windows 7 (64-bit)
frn-client-win7.exeherunterladen und in einen eigenen Ordner legen.- Start the EXE – no installation required.
- In the Settings tab, enter call sign, email, password, server, port and network.
- Save and Connect.
- Hold PTT, speak, release.
Der Client schreibt bei Bedarf frn-client.log neben die EXE. Diese Datei hilft bei Anmeldeproblemen.
Windows XP (32-bit)
frn-client-xp.exeherunterladen und in einen eigenen Ordner legen.- Start the EXE – no additional runtime.
- Enter call sign, email, password, server, port and network.
- Save and connect.
- Hold PTT, speak, release.
The XP client uses the default Windows audio device. If you have several sound cards, set it in the Control Panel before starting. With admin rights, administration, access list and HTML info are available.
Android
Install and connect the app.
The Android app is distributed as an APK. It does not connect automatically – you start the connection yourself and can leave it running in the background.
1. Install the APK
Lade die Android-APK herunter. Erlaube in den Android-Einstellungen einmalig die Installation aus unbekannten Quellen und öffne die Datei.
2. Open the settings
Enter server, port, network, call sign, email and password. The server directory is optional; for protected servers you need the operator's credentials.
3. Connect and allow the microphone
Tap Connect. The first time, Android asks for microphone access. Without this permission the app cannot transmit.
4. Push-to-Talk
Hold down the large PTT button and speak. Releasing ends the transmission. The status line shows receive and transmit.
5. Chat and background operation
Chats gives you access to group calls and private conversations. The connection stays active in the background; a notification offers the Disconnect action.
6. Status and administration
Im Hauptfenster wählst du oben den Status online, beschäftigt oder abwesend. Bei Adminrechten erscheint unter der PTT-Taste der Button Administration. Langes Drücken auf einen Clientnamen öffnet Sperren/Entsperren und Stummschalten/Unmute. Die Adminlisten Zugang, Admins, Gesperrt und Stumm liegen in eigenen Tabs.
7. Installing updates
Under Settings → Check for updates, the app shows available versions. One tap downloads the APK, verifies the SHA-256 checksum and starts the installation.
8. Any device button as PTT
Under Settings → PTT button you can assign any device button that Android passes to the app – for example volume up/down, extra buttons, Bluetooth media buttons and, depending on the device, the power button.
Foreground only: the assignment applies while the app is in the foreground. The button then triggers push-to-talk. When the app is in the background or closed, the button returns to its normal function – changing the volume, locking the screen and so on.
To assign a button, press “Assign PTT button” and then the button you want. “Clear PTT button” removes the assignment. The on-screen button remains usable regardless.
Not every Android version passes every button to apps. The power button therefore works depending on the device and system version.
Quitting: “Quit program” logs the client out of the server, stops the background service and removes the app from the overview.
Server
Running your own server.
FRN Server 0.22 runs on Debian/Linux, Windows 10/11, Windows 7/XP and Fedora/RedHat. You can use the GUI or the headless system service. A database or additional runtime is not necessary.
1. Download the server package
Download the package for Debian/Linux, Windows 10/11 or Fedora/RedHat. Windows 7/XP have their own packages on the server page.
2. Configure the operator and server
Start the GUI. Under Operator, enter email, call sign, name, country, location and the manager password. Under Server, select the IP version (4, 6 or 46), the listen ports, the port reported to the manager and the default network.
3. Choose the manager mode
FRN / F / 3 checks every client strictly; if the SystemManager is unreachable, the login is refused. Light / L / 2 permits login if the manager is briefly unreachable. Notify / N / 1 only sends status messages. Standalone / S / 0 uses no manager.
4. Networks and permissions
For each network you set MaxClients, MaxSpeechTime, SpeechPause, Parrot, HiddenNet, Charset, ManagerMode, ManagersMask, AccessInfoMode, OutputBufferLimit and LogClientLevel. The access list and info message are edited directly in the network. Simple HTML in the info message is supported.
5. Save and start
Click Save and then Start. On first start a default configuration is created; third-party credentials or sample accounts are not imported.
6. Set up as a system service
Under Server → Set up as a system service or in the Service tab, the GUI sets up the systemd service, starts it and enables it at boot. Alternatively from the console:
sudo frn-server install-service --config /etc/frn-server/server.json
Entfernen: sudo frn-server remove-service. Zustand und Konfiguration bleiben bei einem Update erhalten.
7. Open ports and test
Gib die TCP-Ports (Standard 10026, weitere Listen-Ports) in Firewall und Router frei. Teste mit einem Client: Teilnehmerliste, Sprache, Text, Administration, Zugangsliste und Info-Nachricht.
8. SystemManager
Der Server meldet sich beim festen SystemManager sysman.freeradionetwork.net:10025. Zusätzliche Manager trägst du im Reiter SystemManager ein. Die Client-Prüfung erfolgt automatisch; IPv4 und IPv6 werden unterstützt.
server.json and state files can contain operational data. Protect them, back them up regularly and start the server only from a trusted source.
Existing systems
Connecting old clients and servers.
The original FRN client and the old Windows server can be connected to the server directory without an update. The current clients and servers need no changes.
Original client (FRNClient.ini)
Öffne die FRNClient.ini und ergänze den Abschnitt oben in der Datei:
[SystemManager]
Address=sysman.freeradionetwork.net
Port=10025
Wichtig: Der originale Client liest die Adresse über den Schlüssel Address und den Port über Port. Es dürfen keine Leerzeichen um das Gleichheitszeichen stehen. Speichere die Datei und starte den Client neu.
Der Abschnitt [SystemManager] ist die historische Bezeichnung des Serververzeichnisses. Er wird nur für die Anbindung gelesen und erscheint nicht in der Oberfläche.
Original Windows server (server.ini)
Beim originalen Windows-Server steht die Anbindung im vorhandenen Abschnitt [Server] der server.ini:
[Server]
ManagerAddress=sysman.freeradionetwork.net
ManagerPort=10025
ManagerMode=FRN
ManagerMode legt fest, wie streng der Server das Verzeichnis behandelt:
FRN/F/3: harte Prüfung; ohne erreichbaren Manager keine Verbindung.Light/L/2: ohne erreichbaren Manager wird der Login erlaubt.Notify/N/1: nur Statusmeldung, keine Login-Prüfung.Standalone/S/0: kein SystemManager.
Other clients and servers
For all other configurable clients and servers, enter the directory directly in the connection data:
| Field | Value |
|---|---|
| Server / Host | sysman.freeradionetwork.net |
| Port | 10025 |
Der Port 10025 ist der Datenport des Verzeichnisses. Die Verbindung zu deinem eigentlichen FRN-Server bleibt davon unberührt.
[SystemManager] or [Server] section and whether port 10025 is reachable.Crosslink
Two networks, one conversation.
Crosslink links FRN servers and networks permanently. You need credentials and a target network for each side. Several crosslinks can run at the same time.
- Download and unpack the Crosslink package for Windows or Linux.
- Start the program and add a new crosslink.
- Side A: enter server, port, network, email, password and call sign.
- Side B: enter the same details for the second network.
- Optionally use the server directory and a dynamic password.
- Connect – both sides log in as a crosslink client.
- Check status and RX/TX packets. Enable monitoring if needed.
- For continuous operation, set up the headless system service and autostart.
Topology: for production use, use a star topology so that audio does not loop. A crosslink connects FRN networks; for radios you need a gateway.
Typical settings
Side A: server A, network A, its own crosslink account.
Side B: server B, network B, its own crosslink account.
Description: filled in automatically with the remote end.
Monitoring: only one crosslink at a time.
Automatic reply: optional for private messages, with a placeholder for your own email address.
The configuration contains passwords in plain text. The file is saved with restrictive permissions.
Gateway in practice
Gateway
Connecting a radio and FRN.
A gateway consists of a radio, an audio interface and a computer with the FRN client. The client carries voice from the radio into the network and vice versa.
- Connect the radio, audio interface and PC as specified by the manufacturer.
- Select the correct input and output device in the client.
- Adjust the level using the test tone and the level meter.
- Connect to server and network.
- Test push-to-talk in both directions.
- Check for feedback and latency before opening the gateway.
- Inform participants about the Internet transmission.
Legal: amateur radio is subject to licensing and call sign rules, CB radio to national regulations. If in doubt, clarify gateway operation with your association or the competent authority.
Help
If something does not work.
Most causes can be narrowed down quickly. First check the server, port, network and audio devices.
No connection to the server
Check the server address, port and network. Watch out for typos and make sure the server is reachable. A firewall may block the port. For protected servers the credentials must be valid.
Login rejected or account already logged in
Check email and password. For a dynamic password, contact the server operator. If the server reports “account already logged in”, the account is still connected to another session.
No sound on receive
Select the correct output device and check volume and mute. On Windows XP the default playback device is used. Use the test tone to check whether the client transmits and plays back.
The microphone does not transmit
Check the input device and the operating system's microphone access. PTT must be held down. On Android, microphone permission must be granted.
Windows SmartScreen warns about the EXE
The clients are not signed with a commercial certificate. Only download the file from this website and compare the SHA-256 checksum. If it matches, you can deliberately confirm the warning.
Android does not install the APK
Allow installation from unknown sources for the file manager or browser. Then open the APK again. The app requires Android 5.0 or later.
The server does not appear in the directory
Check whether the server is running, whether the public address and port are correct and whether registration with the system operator has taken place. Without a directory, the server remains reachable via its direct address.
The server does not start or does not listen
Prüfe im Reiter Server IP-Version (4, 6 oder 46) und Listen-Ports. Bei IPv6 muss [::] als Dual-Stack gebunden sein. Prüfe außerdem Firewall/Router und ob der Port bereits belegt ist. Die Logdatei steht unter dem eingestellten Pfad, der Dienst loggt über journalctl -u frn-server.
Windows blocks the server
The EXE is not signed with a commercial certificate. Only download the package from this website and check the SHA-256 checksum. Windows may show a warning on first start.
Audio loops with Crosslink
A triangular topology can make audio run in a loop. Instead, connect the networks in a star shape via a central network.