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 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
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.
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 http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
Assuming a rural mountaintop location, this might not be real convenient. The dedicated box would allow it to be anywhere on the planet with reasonable internet service. The only restriction is that the cooperative person involved must not be running EchoLink himself. Ciao Ken From: Jim Duuuude [mailto:telesistant@hotmail.com] Sent: Saturday, April 09, 2011 11:20 PM To: ke2n@cs.com; Chuck Henderson Cc: app_rpt mailing list Subject: RE: [App_rpt-users] 2 systems on one LAN, each with an Echolink number 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 http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
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 http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
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
I like Jim's idea. But add a Virtual Interface to your network card. "eth0:1" Your LAN can handle many different networks. If your running a Linux router you can have lots of fun running two WAN's. Or ask your ISP for a second IP address. How about using a USB CDMA card "Virgin Mobile Cheap" on the mountain top for the second computer. Then you could just route the EchoLink out the USB CDMA card and use it as a fail over route. David On Sat, Apr 9, 2011 at 8: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 http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@ohnosec.org http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
participants (5)
-
Chuck Henderson -
David KE6UPI -
Jim Duuuude -
K&R Yoksh -
Ken