| Sorry for sparse information and delay. I had walked away from this project for a few days... I have two WRT54Gs configured  with HSMM-MESH 0.3.3-WRT54G firmware.  Node 1 is configured as a gateway and is connected to my home router  where it receives a DHCP-provided IP on the WAN port. Node 2 is also  located at my home QTH for testing. My Asterisk server is attached to  the LAN port of Node 2. For testing, target nodes are all DMZ’d. IAX2  and HTTP work across the mesh. My Echolink node shows to be logged in  and active, but I cannot connect to other Echolink stations, nor can any  Echolink station connect to me. Echolink is not in use on any other  computers at the time of testing. Thinking that I must have HSMM-MESH configured improperly, I  temporarily replaced the Asterisk server (where Echolink resides) with a  laptop running Windows Echolink software.  The laptop was set to the  same static IP as the Asterisk server. The Echolink software test shows  that UDP ports fail. TCP ports pass. However, upon further  investigation, it appears that Echolink validates the private IP of HSMM-MESH Node 2, rather than the public IP assigned by my ISP. I hope that helps clarify what I’m attempting to do… everything works  as it should if I bypass the HSMM-MESH nodes and connect to my home  network. I'm hearing from some that Echolink will not work across a mesh  network. If that's the case, there are some fairly easy ways to  work-around the problem. I am just curious if others are successful  where I have failed. |