you have to add a second instance stanza in the echolink.conf file (name it something like el1 instead of el0) and in BOTH stanzas you need to specify ipaddr= to bind each one to its associated IP address. Also, if you happen to have a NAT router that is behind more then one public IP that is capable of doing explicit public IP/port to private IP/port NAT bindings, you can have both instances on the same local IP address, but specify port= in both cases and put the second (or third or fouth, etc) on some strange port number (the port= specifys the lower number of the port number pair to be used) and then bind the other addresses to other public IP addressses on their normal public port (5198 I guess it is). In any case, each stanza would have different echolink login info, and also, have a different app/rpt node associated with it. For outbound traffic, all connections come from the Echolink node node number associated with el0. Remember, this is not archetected like a normal Echolink installation. Multiple inbound and outbound connections are supported completely and independently of each other. JIM WB6NIL From: rpt2@chuck.midlandsnetworking.com Date: Sun, 10 Apr 2011 01:54:50 -0500 Subject: Re: [App_rpt-users] 2 systems on one LAN, each with an Echolink number To: telesistant@hotmail.com CC: ke2n@cs.com; app_rpt-users@ohnosec.org Jim,Interesting, so if I have 2 internet connections, one with a lan 192.168.168.0/24 and the other with a lan 172.16.16.0/24 and I have a server with 2 ip addresses configured, 192.168.168.168 and 172.16.16.16, so far the easy stuff for me. What configuration needs to be done (in echolink.conf I suspect) on that server for 2 independent echolink nodes so that one uses one address and the other uses the other address? Chuck On Sat, Apr 9, 2011 at 10:19 PM, Jim Duuuude <telesistant@hotmail.com> wrote: Well if youre going to get one of your neighbors involved, why dont you just get their permission (of course) and have a wireless device on their network and either put it on your existing LAN (assuming their local LAN netblock is different then yours) or put in a second NIC card or something. chan_echolink is perfectly capable of running as many Echolink nodes as you have (public) IP addresses on your server.
From: ke2n@cs.com
To: rpt2@chuck.midlandsnetworking.com Date: Sat, 9 Apr 2011 23:15:34 -0400 CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] 2 systems on one LAN, each with an Echolink number
Convince one of your neighbors to run an asterisk box at his house. (a mini itx in the basement - he will forget it is even there)
The only thing on that box will be the E/L channel. Then permalink your second node to this "E/L Hub". Done.
Ken
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.
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org