[App_rpt-users] ACID/Echolink On HSMM-MESH Network

Jim Duuuude telesistant at hotmail.com
Mon Sep 6 11:47:59 EDT 2010

Your network is obscuring the real IP address of the incoming packets. Normally, even in
a NAT-ed environment, incoming IP packets bear the real, true address of their origination
and thats what  we validate on. In a network like that, that changes the IP address of the
incoming packets, this stuff just isnt going to work, since it needs the REAL IP address to
validate on.


> Date: Mon, 6 Sep 2010 06:30:32 -0700
> From: wb5nfc at yahoo.com
> To: app_rpt-users at qrvc.com
> Subject: [App_rpt-users] ACID/Echolink  On HSMM-MESH Network
> I am attempting to configure a node to operate as part of an experimental 
> HSMM-MESH network. I am using the latest ACID distro. Ports 5198-5199, 5200 and 
> 4569 are forwarded across the mesh. Chan_echolink downloads echolink nodes 
> properly from the Echolink server and my node appears on the Echolink list of 
> active nodes. When I attempt to connect (from an outside network) I receive 
> "Connection Failed. Cannot connect to WB5NFC-R. UN-AUTHORIZED." From the 
> Asterisk CLI the error appears as: ERROR[2356]: chan_echolink 2185 do_new_call: 
> Cannot find DB entry for b/ipaddr/10.245.130.XX (the Wi-Fi IP of the first 
> router in my HSMM-MESH. I suspect I need to edit a config file someplace to 
> account for the mesh operation, but I'm not sure where/what. Suggestions 
> appreciated.
> John / WB5NFC
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20100906/56f058e6/attachment.html>

More information about the App_rpt-users mailing list