10th Anniversary Giveaway!

On April 30th, it will be ten years since the "W2LJ - QRP - Do More With Less" blog was born.

In appreciation for all who read this blog, I am going to give something away to one lucky reader. I have a new, mint condition, unused, complete sheet of fifty United States Amateur Radio stamps, issued in 1964 on the 50th Anniversary of the ARRL - Scott #1260. I am going to have the sheet matted and framed - ready for display on some deserving shack wall. All I ask is that you send an e-mail to w2lj@arrl.net - entitled "Blog Anniversary Giveaway". Include your name, call sign and mailing address.

Any Amateur Radio op worldwide can enter. I will package and ship the framed stamps to any destination that the United States Post Office will accept.

The names and call signs will be loaded into a software program such as RandomPicker on April 30th and a winner will be determined. The winner will be announced here, and then the framed stamps will be posted.

Good luck, and thank you for reading!

Friday, December 19, 2008

Got it figured out!

OK - I seem to have gotten it figured out. I was able to get on the "Echotest" server successfully and listen to some test transmissions.

These are the steps I followed - they may or may not work for you. I am using Verizon DSL.

1) Start up Echolink and go to the "Help" menu.
2) Type in "DSL" and hit search topics - this is the part you will be most interested in:

Firewall Issues

EchoLink uses UDP ports 5198 and 5199. To use EchoLink, you must configure your router to direct all incoming data on these two ports to the PC on which EchoLink is installed. Typically, there are two ways to configure this:

  • Forwarding. Most routers allow data on specific ports to be "forwarded" to specific computers. If you expect to use EchoLink on only one PC, configure your router to forward UDP ports 5198 and 5199 to that computer.
  • Port triggering. Some routers implement a "smart" forwarding scheme which tries to direct data to the computer which is most likely to use it, based on requests each computer has recently made. If you expect to use EchoLink any of several different computers at different times, you may wish to try this option. Configure the router to direct ports 5198 and 5199 to any computer which makes outbound requests over UDP ports 5198 or 5199, or TCP port 5200.

EchoLink also uses TCP port 5200. Most routers will handle these requests correctly, since EchoLink always initiates them from the local computer. If you are using firewall software, however, you may need to "open up" outbound connections to this port. (EchoLink does not use TCP for incoming connections.)

Go to http://www.portforward.com and look for the make and model of your DSL modem. Type the IP Address in as a URL. In my case it was http://192.168.1.1 (yours will probably be different) in a blank browser window. BIG TIP: Use "admin" as the user name and use "password" as the password to log into your DSL modem. Using "admin" as both the user name and password will not allow you "in" to your modem! At this point, do not try to customize the firewall setting of your modem! Instead, I was able to go to a tab that said "Enable Applications". I opened this and added Echolink as a new application. I entered the Echolink recommended values for Port Triggering and Port Forwarding, saved this as a new application and Viola!, I can now use Echolink for my weekly chats with W3BBO.

Truth be told, I only have a vague idea of what I actually did! All I know is that Echolink now works; and I didn't seem to do any damage to anything else.

Maybe ignorance is bliss!

73 es Good Luck if you're as new to this as I am,

Larry W2LJ

No comments: