Cellular backup connections

Fri Dec 28 18:32:17 UTC 2018

I found horrible routing with a static IP setup with T-Mobile. The device
was located in Ashburn, outbound routing would go out via Dallas and
inbound would come in via Seattle. So ping times and usability was rough.
Tried it on the west coast and the same problem. T-Mobile support said this
was by design and they couldn’t change it.

I decided to switch to a regular consumer AT&T data sim without a static IP
and set up a small router to initiate a VPN tunnel out to wherever I need
it. It turns out to be cheaper and reliable for us.

~Jared Geiger

On Fri, Dec 28, 2018 at 11:53 AM Ryan Wilkins <ryan at deadfrog.net> wrote:

> You mention your connection is 4G.  On T-Mobile 4G is UMTS whereas LTE is,
> well, LTE.  Are you really on UMTS (which I would expect to have much
> crazier RTTs and jitter like you report) or did you mean LTE?
>
> Ryan
>
> > On Dec 28, 2018, at 7:06 AM, Dovid Bender <dovid at telecurve.com> wrote:
> >
> > Hi All,
> >
> > I finally got around to setting up a cellular backup device in our new
> POP. I am currently testing with T-Mobile where the cell signal strength is
> at 80%. The connection is 4G. When SSH'ing in remotely the connection seems
> rather slow. Ping times seem to be all over the place (for instance now I
> am seeing: rtt min/avg/max/mdev = 174.142/336.792/555.574/99.599 ms) . Is
> that just cellular or is that more related to the provider and the location
> where I am? I could in theory test with VZ and ATT as well. With Verizon
> they charge $500.00 just to get a public IP and I want to avoid that if
> possible.
> >
> > Thanks and sorry in advance if this is off topic.
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20181228/b7093048/attachment.html>