[App_rpt-users] Multiple Echolink Server side

[Chuck Henderson]

I have not tried any of this and do not know if it will work, but I think
it will.

If your server has real IP addresses, not NATed in a firewall router, then
you can create different echolink stanzas within echolink.conf and in each
one put a different IP address.  If you are NATed then you will have to
know how to do policy routing in your professional router, like a Cisco
router or maybe a routerboard.

The default if it is not configured is
ipaddr=0.0.0.0

But you would make it
[el0]
ipaddr=8.9.10.11
all the other commands

[el1]
ipaddr=8.9.10.12
all the other commands

[el2]
ipaddr=8.9.10.13
all the other commands

There are a couple of people on here that know if I have this correct or
not, but I don't know.  Let us know if this works, if you feel like
experimenting.
Chuck  WB9UUS




On Wed, Jul 29, 2015 at 10:16 PM, David McGough <kb4fxc at inttek.net> wrote:

>
> 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 at gmail.com
> > Phone: 618-553-0806
> > http://www.lorentedford.com
> > http://www.kc9zhv.com
> > http://hub.kc9zhv.com
> >
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to the bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150729/bcd6ccc4/attachment.html>