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
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
On Fri, Dec 28, 2018 at 07:07:42AM +,
Erik Sundberg wrote
a message of 131 lines which said:
> CenturyLink will be conducting an extensive post-incident
> investigation and root cause analysis to provide follow-up
> information to our customers
Is this problem also responsible for the
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
> 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
>
Check the route your taking when you use the cell phone as a hotspot and when
you use the LTE modem. The carrier may be using different paths.
You may want to engage the vendor of your modem as well to make sure everything
in it is configured correctly. Depending on the device there are a lot
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
I’ve found the antenna choice and placement can make a huge difference in a
data center environment. In some cases it required going to a directional high
gain antenna pointed towards a desirable tower, which we found by having
someone monitor / reload the Opengear web interface while another
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
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
> 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
This is an automated weekly mailing describing the state of the Internet
Routing Table as seen from APNIC's router in Japan.
The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG
TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG.
Daily listings are sent to
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
Looks like we lost sync intermittently across several of their servers last
night. Cleared up around midnight mountain for me.
Let's chip in and get some carrier diversity for those guys :)
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, December 28, 2018 4:23
Yes, there were 911 services affected. The latest word from C-link as of 1:46PM
mountain is that all 911 services are restored where they are the provider. I'm
not 100% sure if that's system-wide, or just my area in the northwest, however.
Sent with ProtonMail Secure Email.
‐‐‐ Original
On Fri, Dec 28, 2018 at 12:05 AM Stephane Bortzmeyer wrote:
> Is this problem also responsible for the 911 outage? If so, the
> post-mortem analysis is not useful only for CenturyLink customers but
> for everyone on the west coast.
Looks like most time.nist.gov servers (3 x NIST sites on AS49)
Thus spake Christian Meutes (christ...@errxtx.net) on Fri, Dec 21, 2018 at
02:41:23PM +0100:
> Depending on your requirements and scale - but I read you want history -
> it's probably less a demand on CPU or network resources, but more on IOPS.
>
> If you cache all results before writing to
And the other latest news is that the FCC is investigating the CenturyLink
outage:
https://www.theinternetpatrol.com/fcc-investigating-centurylink-outage-says-unacceptable/
> On Dec 28, 2018, at 3:11 PM, Patrick Boyle via NANOG wrote:
>
> Yes, there were 911 services affected. The latest
Ouch. Feel bad for the guys on the ground at C-link. Not a fun 24 hours.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Friday, December 28, 2018 3:17 PM, Anne P. Mitchell, Esq.
wrote:
> And the other latest news is that the FCC is investigating the CenturyLink
>
19 matches
Mail list logo
