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

[TJ]

John

 

I went back and checked the portal to refresh my memory and the only network configuration options that are available,  are for your servers internal ip address. It should be set to the network behind the router ie: 192.168.X.X if it is set to no-ip then when you download the config to your node it would not have a ip address and could not communicate to your router because they are on differing networks. 

 

Because you are running through a VPN tunnel and the way DHCP servers work. I would tell you to set your server ip address to DHCP if your router is providing dhcp services. 

 

To do so go to the portal then choose server, server configuration, then click on your server name. 

 

When the server configuration page opens click on network configuration then change the third line to DHCP.

 

If your router does not provide DHCP then change this line to Static and put in a static IP that is on your network behind the router. 

 

If your routers ip address is 192.168.1.1 then use something like 192.168.1.10 if your router is using a different IP scheme just make sure the first three groups of numbers are the same.

 

 

I think this is why you cannot make any connections. 

 

A little more info on VPN tunnels:

 

The way a VPN works is it creates an encrypted connection between your node and the VPN server. If all of your traffic is being sent over the VPN,  then the IP address that is seen by everyone on the net is the IP address that was assigned to your VPN servers network by their service provider. So it would not matter if you used Verizon or AT&T because you would always be getting to the net via IPvanish. 

 

If you router is configured to use the IPvanish tunnel and it is routing all of your traffic over the the VPN tunnel then your configuration on the node is good and it would not matter what service provider you are using. You could switch from any service provider without making any changes. 

 

That being said you can configure your router to send all your traffic through the VPN or only part of the traffic. If only part of the traffic is running through the VPN Then switching between AT&T and Verizon could create problems depending on what traffic was not going through the VPN tunnel. 

 

TJ (KL3IT)

 

 

From: arm-allstar-bounces at hamvoip.org [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of John
Sent: Thursday, August 28, 2014 12:21 PM
To: BeagleBone Black ARM Allstar
Subject: Re: [arm-allstar] Echolink Still Not Working....

 

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 <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





 

-- 
John Kenney 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140830/cfb13780/attachment.html>