« previous next »
Pages: [1]   Go Down

Author Topic: Connection woes  (Read 1183 times)

Offline Smut

  • Copper Member
  • **
  • Posts: 195
Connection woes
« on: April 14, 2000, 04:55:00 PM »
Not sure if anyone at HTC can do anything with this info, but here it is:

04/14/00 17:52:16 ping beta.hitechcreations.com
Ping beta.hitechcreations.com (216.91.192.19) ...
  1  Addr:216.91.192.19, RTT: 422ms, TTL: 244
  2  Addr:216.91.192.19, RTT: 419ms, TTL: 244
  3  Addr:216.91.192.19, RTT: 439ms, TTL: 244
  4  Addr:216.91.192.19, RTT: 429ms, TTL: 244
  5  Addr:216.91.192.19, RTT: 486ms, TTL: 244
  6  Addr:216.91.192.19, RTT: 438ms, TTL: 244
  7  Addr:216.91.192.19, RTT: 497ms, TTL: 244
  8  Addr:216.91.192.19, RTT: 462ms, TTL: 244
  9  Addr:216.91.192.19, RTT: 450ms, TTL: 244
 10  Addr:216.91.192.19, RTT: 451ms, TTL: 244

04/14/00 17:54:22 Fast traceroute beta.hitechcreations.com
Trace beta.hitechcreations.com (216.91.192.19) ...
 1 24.5.95.1        32ms   44ms   25ms  TTL:  0  (No rDNS)
 2 24.3.0.1          6ms   42ms   15ms  TTL:  0
(r1-fe0-0-100bt.twsn1.md.home.net bogus rDNS: host not found
[authoritative])
 3 10.0.236.5       14ms   20ms   20ms  TTL:  0  (No rDNS)
 4 24.7.74.9        21ms   26ms   16ms  TTL:  0  (c1-pos5-1.bltmmd1.home.net
ok)
 5 24.7.65.221      27ms   24ms   18ms  TTL:  0  (No rDNS)
 6 144.232.8.93    461ms  467ms  452ms  TTL:  0
(sl-bb12-pen-0-3.sprintlink.net ok)
 7 144.232.9.238   465ms  496ms  488ms  TTL:  0
(sl-bb11-fw-5-2.sprintlink.net ok)
 8 144.232.11.5    470ms  484ms  465ms  TTL:  0
(sl-bb11-fw-8-0.sprintlink.net ok)
 9 144.232.11.66   460ms  491ms  477ms  TTL:  0
(sl-gw13-fw-8-0-0.sprintlink.net ok)
10 144.228.137.6   470ms  493ms  479ms  TTL:  0
(sl-dnetfw-1-0-T3.sprintlink.net ok)
11 216.90.2.66     459ms  523ms  507ms  TTL:  0
(applink-1.usdlls.savvis.net ok)
12 216.91.192.19   472ms  490ms  502ms  TTL:244  (beta.hitechcreations.com
ok)

This is with a cable modem, no less!

-Smut



------------------
XO, The squealing Pigs
"Oink! Oink! To War!"
Logged

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Connection woes
« Reply #1 on: April 15, 2000, 11:05:00 AM »
 
Quote
Originally posted by Smut:
Not sure if anyone at HTC can do anything with this info, but here it is:

04/14/00 17:52:16 ping beta.hitechcreations.com
Ping beta.hitechcreations.com (216.91.192.19) ...
  1  Addr:216.91.192.19, RTT: 422ms, TTL: 244
  2  Addr:216.91.192.19, RTT: 419ms, TTL: 244
  3  Addr:216.91.192.19, RTT: 439ms, TTL: 244
  4  Addr:216.91.192.19, RTT: 429ms, TTL: 244
  5  Addr:216.91.192.19, RTT: 486ms, TTL: 244
  6  Addr:216.91.192.19, RTT: 438ms, TTL: 244
  7  Addr:216.91.192.19, RTT: 497ms, TTL: 244
  8  Addr:216.91.192.19, RTT: 462ms, TTL: 244
  9  Addr:216.91.192.19, RTT: 450ms, TTL: 244
 10  Addr:216.91.192.19, RTT: 451ms, TTL: 244

04/14/00 17:54:22 Fast traceroute beta.hitechcreations.com
Trace beta.hitechcreations.com (216.91.192.19) ...
 1 24.5.95.1        32ms   44ms   25ms  TTL:  0  (No rDNS)
 2 24.3.0.1          6ms   42ms   15ms  TTL:  0
(r1-fe0-0-100bt.twsn1.md.home.net bogus rDNS: host not found
[authoritative])
 3 10.0.236.5       14ms   20ms   20ms  TTL:  0  (No rDNS)
 4 24.7.74.9        21ms   26ms   16ms  TTL:  0  (c1-pos5-1.bltmmd1.home.net
ok)
 5 24.7.65.221      27ms   24ms   18ms  TTL:  0  (No rDNS)
 6 144.232.8.93    461ms  467ms  452ms  TTL:  0
(sl-bb12-pen-0-3.sprintlink.net ok)
 7 144.232.9.238   465ms  496ms  488ms  TTL:  0
(sl-bb11-fw-5-2.sprintlink.net ok)
 8 144.232.11.5    470ms  484ms  465ms  TTL:  0
(sl-bb11-fw-8-0.sprintlink.net ok)
 9 144.232.11.66   460ms  491ms  477ms  TTL:  0
(sl-gw13-fw-8-0-0.sprintlink.net ok)
10 144.228.137.6   470ms  493ms  479ms  TTL:  0
(sl-dnetfw-1-0-T3.sprintlink.net ok)
11 216.90.2.66     459ms  523ms  507ms  TTL:  0
(applink-1.usdlls.savvis.net ok)
12 216.91.192.19   472ms  490ms  502ms  TTL:244  (beta.hitechcreations.com
ok)

This is with a cable modem, no less!


As I have explained, somewhere in the general section of the BBS, cable modem networks use gateways to the Internet.
Notice how many hops you took inside the @home network, before you actually reached a gateway to the Internet (6).
The cable networks are built like giant private WAN's with gateway access points to the Internet.
In the above case, you hit the Sprint gateway from @home, which appears to be a pretty small pipe.

Sprint has a pretty ugly network topology.  Notice there are 5 hops once it gets into the local D/FW area, before hitting Savvis.  That is just poor routing.

Knowing the naming convention Sprint uses, it looks like they have a dual T1 into the @home network, which is pretty small, considering the size of the @home network.

I think most folks on a cable network will notice very large delays at the gateway points of the cable modem networks.

From what I have seen here that appears to be holding true.

Hope this helps.



------------------
Roy "Skuzzy" Neese
President, AppLink Corp.
http://www.applink.net
skuzzy@applink.net
Logged
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline Smut

  • Copper Member
  • **
  • Posts: 195
Connection woes
« Reply #2 on: April 15, 2000, 11:46:00 AM »
Thanks Skuzzy...something was definately wrong when I did those pings. I'm back to 80-170ms pings to HTC today. Just surprised me because my connect had be rock solid in beta. Figures first day I sign up for pay the net goes south on me.

-Smut
Logged

Offline Pyro

  • Administrator
  • Administrator
  • *****
  • Posts: 4020
      • http://www.hitechcreations.com
Connection woes
« Reply #3 on: April 17, 2000, 08:26:00 AM »
Lots of people coming through Sprint were really messed up last week.  I haven't heard whether it's been fixed yet.



------------------
Doug "Pyro" Balmos
HiTech Creations

Perfect plans, aren't.
Logged

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Connection woes
« Reply #4 on: April 17, 2000, 08:49:00 AM »
You are correct Pyro.  Unfortunately, with Sprint it seems to be terminal.

I have yet to see Sprint be consistent for a period of time exceeding 1 week.

A couple of weeks ago, UUNet practically shut down the peer points with Sprint, as Sprint was broadcasting thier Class C sub-net routes in the BGP tables.  A big no-no.


------------------
Roy "Skuzzy" Neese
President, AppLink Corp.
http://www.applink.net
skuzzy@applink.net
Logged
Roy "Skuzzy" Neese
support@hitechcreations.com

Offline -moto-

  • Zinc Member
  • *
  • Posts: 41
Connection woes
« Reply #5 on: April 18, 2000, 12:32:00 AM »
I guess Im the only one that had a good connection with sprint. since last weeks
switch to alternet. My connx seems to have gone south   can we say lag. ping times were
around 90-100ms on sprint, Now up to around
300-400-ms. route checks show some burps half way through on three of the altnet stops.


Moto  **MOL**
Logged

Offline Skuzzy

  • Support Member
  • Administrator
  • *****
  • Posts: 31462
      • HiTech Creations Home Page
Connection woes
« Reply #6 on: April 18, 2000, 08:24:00 AM »
Actually, when you see your routes suddenly change from one backbone (Sprint) to another (UUNet), it is usually due to the backbone provider (Sprint) having problems.

When this occurs, the backbone (UUNet) that suddenly has to carry the other backbone providers (Sprint) traffic, gets overwhelmed until the other backbone (Sprint) gets thier service back online.

This is your basic Internet fart.  When something likes this occurs, it usually is followed with up to a 30 minute outage, while route propagations occur throughout the Internet.

BTW, I don't just post information to explain what is going on.  Before I made this post, for example, I called UUNet and Savvis to get a better understanding of what may be happening.  If I don't get a satisfactory answer, I have been known to drive over to the Internet hub location(s) and knock on doors until I get an answer  .


------------------
Roy "Skuzzy" Neese
President, AppLink Corp.
http://www.applink.net
skuzzy@applink.net
Logged
Roy "Skuzzy" Neese
support@hitechcreations.com
Pages: [1]   Go Up
« previous next »