<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
okay Kyle... we'll keep you all happy n stuff... :-)<br><br>What I did to attempt to address both of these needs is add a <br>parameter in each node stanza in 'rpt.conf', called<br>'eloutbound'. If, in rpt.conf for a particular node, you<br>specify 'eloutbound=el1', *that* node will make its<br>outbound echolink connections through el1. Any/other<br>nodes that do not have 'eloutbound' specified will do<br>the default thing (use el0). This is available in the<br>app_rpt.c that will be publically accessible when the<br>SVN updates at 14:15 PDT today.<br><br>JIM WB6NIL<br><br><br><div>> From: yokshs@sbcglobal.net<br>> To: app_rpt-users@ohnosec.org<br>> Date: Sun, 31 Jul 2011 15:21:46 -0500<br>> Subject: Re: [App_rpt-users] Multiple Echolink Nodes<br>> <br>> > Secondly, *all* outbound connections from app_rpt originate from el0.<br>> <br>> This works beautifully for my purposes. I have 2 RF nodes and a hub node <br>> here.. To provide Echolink functionality for both nodes, I have Echolink <br>> connected to the hub node (2210). Outbound connections from either RF node <br>> work seamlessly.<br>> <br>> Inbound Echolink calls hit the hub node only, unless a RF node is <br>> specifically connected to the hub node. I'm able to avoid the Echolink <br>> "drive-by" connect/disconnects in this way.<br>> <br>> I can understand others wanting a different configuration, such as the <br>> multiple IP setup that Jeremy described, but hopefully the current <br>> configuration will also remain? Please don't "fix" this! hi hi<br>> <br>> 73.<br>> <br>> Kyle<br>> K0KN<br>> <br>> <br>> --- Original Message ---<br>> <br>> ok.. first of all, echolink protocol requires a one-on-one correspondence <br>> between node number<br>> and public IP address. The "multiple instance" architecture of chan_echolink <br>> is only for systems<br>> that have multiple public IP addresses on them.<br>> <br>> Secondly, *all* outbound connections from app_rpt originate from el0.<br>> <br>> JIM WB6NIL<br>> <br>> <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></div> </div></body>
</html>