Welcome to Handiham World.

You can do it!  
Today, just as we did last week,  we are going to begin with Troubleshooting 101 as part of our initiative to help new ham radio operators (and even some of us older ones) learn how to do some basic troubleshooting for ourselves. Yes, it can be tempting to ask someone else to do things for us.  This can become a bad habit when it keeps us from learning new things, especially things that we could – with a bit of practice – learn to do for ourselves.  Knowing these basic things can serve us well in the future when no help is available.  

Troubleshooting 101

Let’s get to today’s troubleshooting question: 
I like using Echolink, and I’ve finally figured out how to forward the ports on my home router to my ham shack computer.  The problem is that I can’t use Echolink on any other computer in the house unless I change all those port forwarding settings or use a public proxy, which isn’t always available.  Is there anything else I can do to make Echolink a little more convenient?
Echolink is pretty addictive, and it’s easy to understand why you would want to be able to use it all around the house, perhaps even on your laptop while seated out on the patio one of these nice upcoming summer days. As you discovered, when you set up your home router to forward ports as described on the Echolink website, the application will then only work on the computer you selected.  The router will happily direct traffic through those open ports, but only to that one specific ham shack computer.  As you discovered when setting up your home router, port forwarding is not something you can do on a moment’s notice.  You have to log into your router’s web-based administration page, go to the advanced settings, and then the port forwarding section. When you make changes to the settings, the router may momentarily drop internet connectivity and perhaps even reboot.  Then it will take a while for everything to settle down and work again.  This can be a major aggravation if you have other users in your household or if your home phone is a VoIP system that depends on the internet being connected. 
Let’s examine our Echolink application’s built-in Firewall test.  You will find it by opening Echolink, going to the “Tools” menu, and arrowing to the “Firewall/Router Test”. Once there, press and the test runs automatically.  If you are blind or just like keyboard commands because they are faster and better than the mouse anyway, simply press and the letter “T” for the Tools menu, then and the letter “F” for the Firewall/Router test, which will start immediately. 
Since you have already told us that your ham shack computer has Echolink working, you should get this “Testing Complete” message that says “Firewall test results: PASS”. 

It is important to know about this handy little tool that is built into Echolink because you are going to use it again on a fairly regular basis once you make a few simple changes to your router settings.  
Now it is time to use your main computer, which is connected by a LAN cable (preferably) to the router, to open the router’s administration page. Depending on your router’s setup, you will need to log in, then go to the advanced settings page and then to the port forwarding page.  This should all seem familiar as you have already done it once.  Next, you will need to uncheck the port forwarding boxes that you already set up.  Yes, I know it seems crazy, but it is a necessary step. Save the settings, then go back to the advanced settings page and choose “port triggering” or “application rules” this time.  It is similar to setting up port forwarding, but there is a BIG difference:  You are opening ports when the Echolink application calls for them to carry traffic, no matter which computer on your network is running Echolink.  This means that when you open Echolink on your wireless laptop while on the patio, the ports will be open to that computer.  When you close Echolink on the laptop and later that evening you go back into the ham shack to use your main computer, Echolink will then work on that one because the ports will be opened by the “trigger” of a call for traffic to that machine.  
I happen to have a D-Link router, so a screenshot of the application rules (triggering) page shows that I have triggered ports 5198 and 5199 for UDP traffic and port 5200 for TCP traffic.  

Now I can save the settings and after that I should be able to use Echolink on any computer on my home network without having to worry about port forwarding.  
There are some things to remember:

1. Only one computer at a time can be running the Echolink application.  If more than one computer is running Echolink, only one of them will actually connect properly.
2. When you close Echolink on one computer, it may take a few minutes for the network to resolve itself back to a neutral state.  If you try to connect Echolink on another machine immediately, it may not work.  Always allow a few minutes between switching machines – Both machines may be running and connected to the network at the same time, which is not a problem.  It is only starting Echolink too soon after just closing it on another machine that can cause problems. 
3. This is where we try our built-in Firewall/Router tests again:
   
   If the network is ready, the tests will proceed normally with a “PASS” and you are good to go for Echolink fun!

Email me at [email protected] with your questions & comments.   But for the record, please remember that I am NOT tech support for Echolink or your home networking equipment since you are there at home and I’m here in Minnesota.  Reading the manual will get you way farther than calling me for sympathetic head-nodding.

Patrick Tice, WA0TDA
Handiham Manager