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