Motorola WR850G Wireless Broadband Router

EchoLink Setup

Updated: 3/12/2005 16:15Hrs

For those who are having trouble with the Motorola WR850G and Echolink... this Buds for you!

First of all, here is my working setup. I am presently using my 850G as a second router on my home network. My primary LAN router is the Linksys  BEFSR41 ver 2, standard 4 port router. The network address is 192.168.1.0 and I have a static IP through SprintDSL. All computers on the network are assigned a static IP address so I don't use DHCP which would be impossible with Echolink anyway!

The 850G is plugged into the Linksys router and is assigned the IP address 192.168.1.188. Don't ask my why all the funky addresses.... just the way I woke up in the morning!

So to get things going, in the Linksys I forwarded the ports 5198 & 5199 UDP to the 188 address for Echolink and TCP port. Below is a screenshot of the Linksys Port Forwarding page. Note that the Linksys doesn't have a "Port Trigger".

Note the line "5198 to 5199", the check is  Protocol UDP and the address is .188 which is WAN address of the Motorola 850G. Then drop down to the last entry "5200 to 5200", Protocol TCP is checked and forwarded to the .188 address of the 850G.

Now onward to the config of the 850g!

Here is the main setup page for the 850G:

The IP address for the wired side of the 850G is 192.168.1.188 and the gateway of 192.168.1.1. The next screenshot is for the wireless side of the 850G:

The wireless side of the 850G is on the 192.168.10.0 network. Even though this configuration is under the DHCP section, DHCP is NOT turned on (no checkmark in the "LAN DHCP enable checkbox"). I gave the EchoLink computer the address of 192.168.10.50 which you will see on the next series of screenshots.

Virtual Server

Here is where you configure your port forwarding for EchoLink:

I called my Virtual server EchoLink. Click on ENABLE checkbox.

• Protocol is UDP.

• Incoming Port is 5198.

• Forwarding IP is 50 (for 192.168.10.50 of course your IP may be different)

• Forwarding Port is 5198

• Click on the ADD button

 You will see your first entry in the table like the above example after you click on the ADD button. Follow the same procedure for Port 5199. For port 5200, change the UDP to TCP in the Incoming Protocol dropdown list. I put the EchoLink Webserver in there so I can view the logs and disable EchoLink in the event of a problem.

Before you exit this screen, click on the APPLY button to save all your changes. This applies to all screens where you make changes

Now on to Port Triggering!

Port Trigger

Last step is to setup Port Trigger.

This section will have two entries since you have the "From-To". As in the above example of ports 5198-5199, select UDP for protocol then click on the ADD button. See example below for Port 5200:

Select TCP for Port 5200 then click on the ADD button. When finished, don't forget to click on APPLY at the bottom of the screen!

That is all there is to it! You can now connect to the test server (or use the handy Echolink test app http://www.echolink.org/troubleshooter.htm) to see if your setup now works. Don't forget to check your firewall application (Zone Alarm, etc) if you use one to allow those ports.

  Questions???? Comments?????   Did I confuse you even more??????????????? Drop me a note!

                            kd4moj AT kd4moj.org

EchoLink Node 1922