app_rpt does not support using Echolink proxy. Echolink does not even seem to support Echolink proxy reliably and consistently :-). Im sure you must have noticed this in the past. JIM
From: yokshs@sbcglobal.net To: app_rpt-users@ohnosec.org Date: Sat, 9 Apr 2011 22:03:12 -0500 Subject: Re: [App_rpt-users] 2 systems on one LAN, each with an Echolink number
I'll second Jon's advice... Another possibility not yet mentioned is to operate a private Proxy server at another location, and configure your second box to use the proxy for Echolink... I did just that back in about 2006 , although not using App-rpt.. It was all we could do at the time, so it was 100% better than nothing.. However, that brings you up to 3 PCs to operate 2 nodes...
Lastly, you could try what I'm doing here.. At my QTH, I operate several Allstar nodes, and my solution was to connect the Echolink node to a hub node (2210). Through experimention, I found that outbound Echolink calls seem to work fine from any node, even when the RF nodes are not connected to the hub node. I'm not sure if that feature was ever planned, but it seems to work! I normally do not connect the RF nodes to the hub node. Nodes 2210-2213 are all running on a single P3/866 MHZ PC.
If I am expecting an inbound Echolink call (almost never), we can connect any or all of the RF nodes to the hub node.
73 for now.
Kyle K0KN Allstar 2210-2215
--- Original Message ---
Based on that info, what you could do is set up 2 Allstar nodes on one box and setup one echolink node. Connect each node to repeater. That way its the same as having 2 boxes (actually simpler) and both nodes can access the echolink.
Jon VA3RQ
On 4/9/2011 7:18 AM, Jim Duuuude wrote:
Well, an installation of Echolink running on 2 nodes behind the same IP address can only be found with the Easter Bunny, Santa Claus, all the left socks that were ever lost in the laundry and competent, reliable drummers.
In other words, it doesn't exist. The design of their protocol simply DOES NOT allow for such a thing. In their world, it's a unique mapping of one node to one IP address at a fixed port number set ONLY. That's it. Over and out.
JIM WB6NIL
------------------------------------------------------------------------ From: rpt2@chuck.midlandsnetworking.com Date: Sat, 9 Apr 2011 04:40:02 -0500 To: app_rpt-users@ohnosec.org Subject: [App_rpt-users] 2 systems on one LAN, each with an echolink number?
I have 2 AllStarLink systems on one LAN. Each is for a separate repeater system with a separate computer. They share a common Internet address. For AllStar they work fine. For EchoLink I can only make one or the other of them work, but not both.
Is there a way to change the port number of one of the echolink nodes so that they can both use the same Internet address? We want them both to be able to have inbound and outbound connections via echolink, independent of each other.
Chuck
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users