Hi Loren, Have you confirmed for certain that this works for connections to/from KC9ZHV-R ??? The reason I mention this is that, just as I found in my testing earlier, both of these nodes (KC9ZHV-L, KC9ZHV-R) are showing up on the 23.239.26.208 IP address in the on-line echolink node database---I just confirmed this minutes ago. So, if this -is- working, I don't know how it is--it's certainly not behaving like a "typical" echolink node connection. 73, David KB4FXC On Thu, 30 Jul 2015, Loren Tedford wrote:
Ok i was able to solve my issues by having 2 public ip addresses to my vps here is what my Echolink.conf looks like.
Hope this helps.. Note that i have them connected to the same allstar node this important i do believe because of the chan_echolink
[el0] ipaddr=23.239.26.208 confmode=no call=KC9ZHV-L pwd=######### name=KC9ZHV Rpt System qth=Olney, IL email=Lorentedford@gmail.com maxstns=800 rtcptimeout=99 node=925514 recfile=/tmp/recorded.gsm astnode=41834 context=radio-secure #server1=server1.echolink.org #server2=server2.echolink.org #server3=server3.echolink.org server1=server1.echolink.org server2=servers.echolink.org server3=nawest.echolink.org server4=backup.echolink.org
#includeifexists custom/echolink.conf #Deny= #permit= #erxgain=-3.0 ; defaults to -3.0 db #etxgain=3.0 ; defaults to 3.0 db
[el1] ipaddr=45.33.1.43 confmode=no call=KC9ZHV-R pwd=############# name=KC9ZHV Rpt System qth=Olney, IL email=Lorentedford@gmail.com maxstns=800 rtcptimeout=99 node=898243 recfile=/tmp/recorded.gsm astnode=41834 context=radio-secure #server1=server1.echolink.org #server2=server2.echolink.org #server3=server3.echolink.org server1=server1.echolink.org server2=servers.echolink.org server3=nawest.echolink.org
Loren Tedford (KC9ZHV) Email: lorentedford@gmail.com Phone: 618-553-0806 http://www.lorentedford.com http://www.kc9zhv.com http://hub.kc9zhv.com