[arm-allstar] Echolink Still Not Working....

[John]

OK, making a little headway here - I think. When I ran out of minutes on my
main (Verizon) hotspot account this week, I switched over to our secondary
Internet source (AT&T). Two totally different providers with two totally
different networks. Because my Verizon account has a static IP, I had
Echolink configured in the Allstar portal on the Verizon static IP. I also
have the Allstar Server Network Configuration (portal) set up with my no-ip
hostname. The router I'm running has no-ip client builtin. But now there is
a VPN involved...

How should the Network Configuration be set in the portal for my node using
a VPN?

J.


On Wed, Aug 27, 2014 at 7:59 PM, John <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
>



-- 
John Kenney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140828/6ee56e06/attachment.html>