Echolink on Linux

As you likely already know, the Echolink team do not provide a native linux solution. The best they offer is run it under wine. And if you run a modern linux distro that is up to date, and have tried to install echolink under wine, you will know that it crashes before the unpacker has done its job. But, fear not there is a solution.

sm0svx has written a native linux Echolink client and server and it can be found at . Now this is not going to be an easy sudo apt-get install, you will have to compile from source and it has a string of dependencies that also need to be accounted for before you do anything.

I run Linux Mint, but these instructions should work for any debian/ubuntu based distro. For others replace apt-get with your package manager commands. Yum on redhat/centos for example.


Step 1: Install all the dependencies:

Step 2: Download the source files:

Step 3: Unpack source and issue the following commands:

Sit back and wait while the software compiles:

Step 4: Run the Software:

And that is it really, you can make install if you want, but i generally run software like this locally from my home directory. QTEL is the echolink client software and svxlink is the server client. Hope this helps,




17 thoughts on “Echolink on Linux

  1. Thank you it 100% worked compiled OK and works OK may I copy your instructions to post onto YouTube my channel with reference to your site and such with thanks this is my first attempt to compile software for Linux mint 17.2xfce 32 bit and very happy regards gw7lop

    1. Glad you found the information useful Steve. By all means make a youtube of how its done, sharing the information will make it easier for others to get echolink on their linux boxes.

  2. Hi Robert
    Looks like I have a lot more to learn before I become proficient with Linux.
    I have only just recently switched from Windblows to Linux.

    Here is where I got confused. cd yourpath/svxlink-14.08.2/src

    I have replaced “yourpath” with /home/bob/echolink and I have created these directories /echolink/svxlink-14.08.2/src: in /home/bob/

    Q what path? where I want the files to end up or where I just downloaded the zip file to?
    Q do I need to create a directory first where I want “echolink” to live?

    Wait, I fixed it myself.

    I moved the into the /home/bob/echolink directory which I just created and extracted it from there. Now the rest of your instructions work and Echolink works.

    Thanks Robert for providing your instructions for us Linux impaired hams. I left this up just in case someone else made the same mistake in trying to be too tidy in their home directory.

    73 Bob vk2byf

    1. Hi Bob, Linux can be a little different if you have not done much command line before. Typically, as long as you are in the right directory, you can issue the commands prefixed with ./ DOT SLASH is shorthand for the full path of where you are currently are.

      Glad you worked it out and have echolink now working on your Linux Box. 73’s

  3. Will this setup work with the “sysop” mode, as opposed to someone just running an Echolink terminal in order to access the Echolink nodes? I tried the sysop setup in WINE. and it would not function, but as a simple client it worked fine. Thank you for your insight and technical prowess!

    1. There are 2 parts to this program Qtel is the client software to make echolink calls, and svxlink which does the server side parts, (Sysop Mode) I have not played with this part of the software, but i believe it should work for setting up an echolink server node.

  4. Hi Robert-

    I used your Echolink on Linux procedures (above). They worked great. The problem I have is when I start the program, after setting, I can not connect to anyone. It seems to be a NAT firewall problem. I looked all over the internet for a solution, but have come up short. The procedure I did on WIN 10 for the Router which worked great, did not work on LimuxMint 17.3.

    Any recommendations?

    73 kb7ypf/Dick

    1. Hmm, most likely issue will be with port forwarding, as long as the ports are forwarded to the machine and are open on the router, it should work fine. Just to ensure they are forwarded to the IP address of the linux box, if you are issuing dynamic addresses to your home network, then linux and windows might have different IP addresses. Using static IP addresses on home networks generally makes life easier for these kinds of things.

      Keep me posted on how you get on with it, just in case someone has the same issue and stumbles onto this site looking for the same help.

      Sorry i cannot be more help,


  5. Hi Robert-

    Thank you for your response. I did find a solution for running EchoLink in Linux, however, I was not able to fix the current (above) problem of not being able to connect to anyone.

    I went to the EchoLink web page and download the latest EchoLink Windows software to my Linux Mint 17.3 Download folder. Having already installed Wine on my computer, it was just a matter of opening the program with the Wine Program Windows Loader and installing it under the Wine directories (this happens automatically).

    After installation I had a nice EchoLink Icon on my desktop. After clicking on the EchoLink Icon, the program came up and I was able to connect to others without issue.

    In case you are wondering, I did not have to make any adjustments to my Router. The way I set the Router up for Win 10 worked with Linux Mint.

    Hope this can help someone else having issues like I did.

    73 kb7ypf

    1. I have not used the software in a while, seems the last few upgrades of Mint have left the program broken, while mine runs and connects, there is no audio and also when attempting to recompile the software it complains about QT5 locations because QT4 is no longer installed. Looks like i will have to play about with this sometime soon and see if i can get it working again on the current version of Mint.



    1. Good to hear it worked well for you to. You must be using an older version of Linux the newest versions have broken things in some of the libraries.

  6. Does anyone have any guidance on how to configure svxlink to talk to the USB radio interface?

    I have a windows XP box running echolink server with a rigblaster nomic for the radio interface. Im trying to eliminate windows and this XP box is my last major hurdle.

    Any links, discussions threads, spells or incantations would be greatly appreciated.

  7. Our club wants to add EchoLink to its repeater. One of these days I will learn NOT to volunteer for projects. The PC that I have to make this work is an aging Lenovo with 512MB of RAM & it had Windows Vista on it when it was given to me.

    I replaced Windows Vista with Ubuntu Server (running in command line mode to reduce the load on the computer), installed SvxLink on it & have a couple of problems.

    The club wants to EchoLink limit access to those who have paid repeater dues & there is a rather long existing USB cable from the room where the PC is located to the room where the repeater cabinet is located (from what I have been told getting approvals to replace the cable are not possible plus there are issues with the repeater itself when making that change.) In addition to limiting access I have the problem of how to configure the USB side of things.

    I have been using Linux for a while but do not consider myself an expert. I was able to get the Windows version of EchoLink running using Wine but that actually leaves me with a lot more problems than I current have

Leave a Reply

Your email address will not be published. Required fields are marked *