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
: Friday, December 28, 2018 at 7:08 AM
To: NANOG
Subject: Cellular backup connections
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 rem
On 12/28/18 7:06 AM, Dovid Bender 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 tim
It's strange. When we use T-Mo on an andriod device the ping times are
30-40 ms. When we try with the modem + raritn console box it jumps to min
of 100+ ms (the modem is high up on top of the rack and we test with the
phones we are on the floor) - Can 5 feet higher make it that much worse?
On Fri
> On Dec 28, 2018, at 7:29 AM, Dovid Bender wrote:
>
> It's strange. When we use T-Mo on an andriod device the ping times are 30-40
> ms. When we try with the modem + raritn console box it jumps to min of 100+
> ms (the modem is high up on top of the rack and we test with the phones we
> ar
nal it should still be
better than a traditional DSL connection for example.
Brian
From: NANOG on behalf of Dovid Bender
Sent: Friday, December 28, 2018 4:29 AM
To: Brandon Martin
Cc: NANOG
Subject: Re: Cellular backup connections
It's strange. When w
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 wrote:
>
> Hi All,
>
> I finally got
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
On the topic of static ip... as a Net Eng of an ISP, and seeing the pains that
we have to endure with our static ip customers , I wonder if static ip
customers actually inadvertently get less optimal treatment than more flexible,
agile and dynamic ip customers ?
I’m saying that since over the
I really can't believe I'm going to say this, but this has been a good
SD-WAN use case for us.
Scott Helms
On Fri, Dec 28, 2018 at 2:30 PM Aaron1 wrote:
> On the topic of static ip... as a Net Eng of an ISP, and seeing the pains
> that we have to endure with our static ip customers , I wonde
> leave them on an old router where they’ve been for years.
I can’t name names obviously, but you’d be astonished how often I see this and
who the big names are.
- Ben Cannon, AS15206
On Fri, 28 Dec 2018, Dovid Bender wrote:
>I finally got around to setting up a cellular backup device in our new POP.
>When SSH'ing in remotely the connection seems rather slow.
Perhaps using MOSH can help make the interactive CLI session less
annoying.
>Verizon they charge $500.00 just to get
All,
Thanks for all of the feedback. I was on site today and noticed two things.
1) As someone mentioned it could be for static IP's they have the traffic
going to a specific location. The POP is in NJ there was a min. latency of
120ms which prob had to do with this.
2) I was watching the ping tim
On 30 Dec 2018, at 2:16 am, Mark Milhollan wrote:
>
> Perhaps using MOSH can help make the interactive CLI session less annoying.
Haven’t looked in a couple of years, but has anybody made mosh work on OpenGear?
Anyone know if Verizon static IP's over LTE have same issue where they
bounce the traffic around before it gets back to the NY metro area?
On Thu, Jan 3, 2019 at 6:46 PM Dovid Bender wrote:
> All,
>
> Thanks for all of the feedback. I was on site today and noticed two things.
> 1) As someone m
All,
I finally got around to putting in a Verizon LTE connection and the ping
times are pretty good. There is the occasional issue however for the most
part ping times are < 50 ms. I have another strange issue though. When I
try to ssh or connect via the endpoints web interface it fails. If I firs
Could be wrong on this but direct SSH on the LTE side may possibly be not
allowed(filtered) and might just be something you could discuss in a ticket
with Verizon.
--
J. Hellenthal
The fact that there's a highway to Hell but only a stairway to Heaven says a
lot about anticipated traffic volu
I am getting the same for SSH and https traffic. It's strange. Where the
response is something small like:
Moved to this https://63.XX.XX.XX:443/auth.asp";>location.
It works But when I try to load pages that are any bigger it fails. Like I
said before I assume it's either an issue with the MTU o
I ran into this problem and Verizon told me that they filter ports 22 and 23 to
help stem the tide of IoT attacks on their networks by cellular-connected phone
and alarm systems. They said their operational model assumes that all traffic
will be encrypted via either SSLVPN or IPSec. I’m using IP
We deploy routers with Verizon LTE failover - for full functionality, make
sure your MTU is 1428 or less, per their specifications.
Here's an example doc from Spirent that talks about it.
https://support.spirent.com/SC_KnowledgeView?Id=FAQ14556
Alex
On Mon, Jun 24, 2019, 7:51 AM Dovid Bender
20 matches
Mail list logo
