BLIND-HAMS Archives

For blind ham radio operators

BLIND-HAMS@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Darren Duff <[log in to unmask]>
Reply To:
For blind ham radio operators <[log in to unmask]>
Date:
Thu, 3 Mar 2011 21:31:56 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (100 lines)
I gues I don't know how to do incuming and outgoing. My rooter just has a
place to put in the service name, either UDP/something else  and then the
ports.

-----Original Message-----
From: For blind ham radio operators [mailto:[log in to unmask]]
On Behalf Of colin McDonald
Sent: Thursday, March 03, 2011 4:49 PM
To: [log in to unmask]
Subject: Re: echo link again.

depending on your router, sometimes you have to forward the UDP ports both
ways...that is, incoming and outgoing UDP...i always do the same with the
TCP port 5200, but I believe it only has to be set up one way...but set them
all for incoming and outgoing and it should work.
I've always managed to get echolink up and running by doing this...and most
of the time, if I just forward the port like the instructions say, it
doesn't work because that only allows for incoming ports and not outgoing or
vice versa.
This usually means you have to make 6 sets of rules...or 4 sets perhaps with
one setting 5198-5199 incoming, 5198-5199 outgoing, and 5200 incoming and
out going.
again depends on your router, but usually you can tell which one you are
setting bassed on the prompts in the router settings.
73
Colin, V A6BKX
----- Original Message -----
From: "Darren Duff" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, March 03, 2011 10:06 AM
Subject: echo link again.


> ok... I now have echolink up and running, but it won't let me connect 
> to the test server. I have tryed to forward the portes menchoned in 
> the help starting port 5198 and ending port 5199. I set them up as UDp 
> ports. I even added port 5200 in my firewall. but still no dice.
>
> Here is the log from the rooter test.
>
> Windows XP Service Pack 3
> Local IP address: 192.168.1.3
>
> Firewall Test Results: FAIL
>
> The test successfully connected to the EchoLink server on TCP port 5200.
> This means that your system's TCP configuration is correct for use 
> with EchoLink.
>
> The tester did not receive a response for some of the UDP tests.  If 
> you have a router or firewall installed, be sure its Port Forwarding 
> feature is correctly set. (See Help for details.) If you have Internet 
> security software installed, be sure it is configured to allow 
> EchoLink to access the Internet.
>
> There appears to be a router between this computer and the Internet.  
> A router normally requires special configuration for use with EchoLink.
>
> For more information, click the Help button above, or see the Firewall 
> Solutions page on the EchoLink Web site.
>
>
>
> Darren Duff.
>
> amateur radio station KK4AHX.
>
> Drummer for The Overflow worship band!
>
> Band web site http://www.theoverflowband.com 
> <http://www.theoverflowband.com/>
>
> Personal Phone: (678)936-6113
>
> Mobile E-mail [log in to unmask]
>
> personal E-mail [log in to unmask]
>
> windows live messenger *no mail please* [log in to unmask]
>
> skype contact duffman31279
>
>
> 
 

_____________ NOD32 EMON 5924 (20110303) information _____________

This message was checked by NOD32 antivirus system http://www.eset.com

 
 

_____________ NOD32 EMON 5924 (20110303) information _____________

This message was checked by NOD32 antivirus system
http://www.eset.com

 

ATOM RSS1 RSS2