<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Well, an installation of Echolink running on 2 nodes behind the same IP address<br>can only be found with the Easter Bunny, Santa Claus, all the left 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 DOES NOT<br>allow for such a thing. In their world, it's a unique mapping of one 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><hr id="stopSpelling">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 number?<br><br>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.<div>For AllStar they work fine. For EchoLink I can only make one or the other of them work, but not both. </div>
<div><br></div><div>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? </div><div>We want them both to be able to have inbound and outbound connections via echolink, independent of each other.</div>
<div><br></div><div>Chuck</div>
<br>_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users </body>
</html>