[arm-allstar] Setting up node on Cellular connection

[David McGough]

Benjamin,

Crypto latency is typically negligible (under 1ms), even on an RPi2/3
system. There is also the additional latency incurred reaching the VPN
provider. With the US tunnels I run, the additional latency I see is as
much as 40ms for SE USA to NW USA tunnels---not enough to be any concern.

As with all VoIP systems, the primary concerns are almost always only 2 
factors---packet loss and network jitter. These concern are independent of 
whether you're running IPv4, IPv6 or a VPN.


BTW, since many users have mobile woes these days, a comprehensive VPN 
solution is in the works.


73, David KB4FXC




On Tue, 22 Jan 2019, "Benjamin Naber via ARM-allstar" wrote:

> Gents,

A VPN may add un-desirable latency from the crypto.

If it works to satisfaction, then ignore this message.

Just as there are folks on IPv4-only (my ISP is only IPv4), using IPIP
6to4 tunnels to get IPv6 connectivity, you can do the same for IPv6 to
IPv4. You will most likely need to make sure the MTU for the tunnel is
1480.

Find the guides for setting up the IPv6 tunnels, and do the opposite.
In this case, you'll be able to use just about any hosted server whom
has a dual-stack IP connection.

You *may* have to get creative with the 'routes' on the endpoint tunnel
router though, you may have to specify a ip -4 route  with a very low
metric to ensure packets going out IPv4 and not 6.

An alternative, perhaps better, on the endpoint tunnel router, ensure
resolv.conf contains ONLY a IPv4 address for DNS queries.

If this stuff is above your head, get learning. This Internet/computer
stuff is going to keep 'evolving' as time goes on. It not beautifully
simple as AM or FM!


Benjamin, KB9LFZ




On Sun, 2019-01-13 at 12:01 -0500, 
> Hi Mike,
> 
> Setting up a Linux-based VPS with a static IPv4 address, on one of
> the
> multitude of available providers, is probably the simplest and
> cheapest
> solution. You should be able to get this running for no more that a
> few
> $$$ per month.
> 
> I'll be glad to help you get OpenVPN running, I use it everywhere.
> As 
> VPN's go, it's much simpler than many.
> 
> The "proxies" mentioned are Asterisk-based proxies, not a general
> purpose 
> proxy.
> 
> I don't foresee trying to support Echolink proxies anytime soon. I've
> got 
> many other projects in the pipeline right now.
> 
> 
> 
> 73, David KB4FXC
> 
> 
> 
> 
> 
> On Sun, 13 Jan 2019, "Mike Sullivan via ARM-allstar" wrote:
> 
> > All, we are switching from a Windows RF-based Echolink setup to
> > Asterisk
> > Allstar with Echolink directly tied into the controller using a
> > RIM-RC210
> > interface. We are using a Verizon cellular hotspot for our internet
> > connection as we have for the past couple years (cheapest landline
> > we can
> > get is $90/mo for DSL on a "commercial property" I told them where
> > to stick
> > it) and currently I am focused on getting Echolink configured to
> > bring it
> > back online. The node is registering with Echolink, but it will not
> > allow a
> > connection. On the Windows based setup, we had to use Echolink
> > Proxy with
> > the proxy on my personal VDS server to get it to work properly.
> > However,
> > from what I understand, the package does not support Echolink
> > Proxy, so we
> > need to find a workaround.
> > 
> > As the configuration stands, the modem (Verizon SmartHub) is
> > configured to
> > DMZ our router's WAN IP (TPLink router/AP combo) and the
> > appropriate ports
> > are forwarded on the router for our RPi node. I have made several
> > attempts
> > to connect from PC, phone, and had other users attempt to connect,
> > but all
> > are timing out. I'm not sure if Verizon is still blocking the
> > needed ports
> > or not.
> > 
> > I know through the configuration file that there is some form of
> > proxy
> > support, but I'm not sure if that's more of an Asterisk based
> > proxy, or a
> > general proxy (I'm fairly new to using RPi's and of course the
> > image) and
> > I've also seen support for OpenVPN, but I have had such a nightmare
> > trying
> > to configure it. Would anyone have any tips/tricks on what to do?
> > Or would
> > anyone know if there will be Echolink Proxy support perhaps down
> > the road?
> > 
> > Mike Sullivan
> > _______________________________________________
> > 
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > 
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > 
> 
> _______________________________________________
> 
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
_______________________________________________

ARM-allstar mailing list
ARM-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2/3 web page - http://hamvoip.org