Hi Loren, I theory this would work, using one public address per Echolink instance. In the server world this type of setup is basically known as multi-homing. However, I don't think the AllStar Echolink driver was written where the developer expected anyone to attempt to perform multi-homing. So, assuming this is true (i.e.: Echolink driver not multi-home aware), the situation is probably much more complicated....I won't delve into the gory technical details of what's needed for multi-homing, but, very simplistically speaking, the application must "remember" what IP address an inbound request came from and then answer back using that same source address. Minimally, I expect some significant NAT (network address translation) trickery with a Linux firewall will be required to pull this off. I'm working feverishly on other aspects of this project right now, but, I'll put this on my list of things to look at, if no one else beats me to it. And, I agree, this would be useful capability. I've got a couple repeaters right now running on the same control PC and separate echolink connectivity to each would be useful. 73, David KB4FXC On Wed, 29 Jul 2015, Loren Tedford wrote:
Hi again its loren was curious on how to setup multiple echolink configurations with the rpt.conf and echolink.conf
On the server side I can get as many ips as needed however my issue is how can i get these services to work together..
I have enough bandwidth and grunt power just need some advice on how to set it up properly.
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Phone: 618-553-0806 http://www.lorentedford.com http://www.kc9zhv.com http://hub.kc9zhv.com