[arm-allstar] Echolink Still Not Working....
TJ
kl3it at kl3it.net
Thu Aug 28 01:55:25 EST 2014
Have you checked the router at the far end of the VPN tunnel that your connecting to?
If your routing your traffic over a VPN tunnel the router on the other end has to have TCP port 5200 and UDP ports 5198 and 5199 allowing inbound traffic to the IP address you are being assigned on the VPN tunnel.
Not sure what VPN server or service your using or what kind of router is at the other end of the tunnel but if you are being assigned an IP address from a DHCP server on the VPN network and the address changes you will run into the same issue because you now have a different address than the router is forwarding traffic to.
Higher end routers can open ports to all addresses on the inside but if you using something like a Linksys router they cannot so you would have to have the VPN server assign you a static address that does not change to prevent this.
Hope this helps Traffic routing can get complex especially in a situation like this where you are using nat over a VPN tunnel If you have questions just let me know.
TJ
From: arm-allstar-bounces at hamvoip.org [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of Joel Jameson
Sent: Wednesday, August 27, 2014 7:14 PM
To: BeagleBone Black ARM Allstar
Subject: Re: [arm-allstar] Echolink Still Not Working....
If you log in to asterisk as "asterisk -rvvv" you will get a pile of logs on your screen, have someone try to log in via echolink while your watching. If you can see them getting in, it's probably not a firewall/port issue. If you don't see them, it's most likely either an IP/DNS mismatch, port, or firewall issue.
Cheers,
Joel
W0KGW
On Wed, Aug 27, 2014 at 8:14 PM, John <wb5nfc at gmail.com <mailto:wb5nfc at gmail.com> > wrote:
Joel,
Thanks for your response. Two different stations, one in Memphis, one in a nearby town tried unsuccessfully to connect. I'm aware of the inability to connect from the same IP. That's why I asked friends to try and connect....
John
Sent from my iPhone
On Aug 27, 2014, at 8:07 PM, Joel Jameson <w0kgw3 at gmail.com <mailto:w0kgw3 at gmail.com> > wrote:
Try using a device not on the same link to connect to it.
To clarify, if it's your "iPhone hotspot" for your BBB data connection, you will need to use a different device with echolink installed that can use another data source (cable, DSL, neighbors wireless, ect) to connect. Then you can watch the logs while connecting and see what's going on.
Cheers,
Joel
W0KGW
On Wed, Aug 27, 2014 at 7:59 PM, John <wb5nfc at gmail.com <mailto:wb5nfc at gmail.com> > wrote:
I thought I had all of the gremlins slain when I got a VPN working on my node. It appears that is not the case. Two different stations tried to connect to my node tonight via Echolink. Neither was successful. My node is listed on Echolink as an active station as well as on Allstar as an active node. How do I begin to troubleshoot this problem? I'm utilizing AT&T on an iPhone hotspot with a Cradlepoint router. When logged in on the BBB, I can ping Echolink servers. What am I missing???
John
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140827/186fc13d/attachment.html>
More information about the arm-allstar
mailing list