dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
9
share rss forum feed


hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
kudos:11
reply to bluepoint

Re: [TWC] Deciphering tracert

"Wrong loosing 15Mbps because of a congested gateway is not acceptable. We are not talking about the last hop. Everyone can reach the last hop but the question is for how fast."

The trace shows exactly how fast you can reach the last hop.

The packet loss is a problem in the first routes with a router, with the router out it looks a lot better.

Much more troubleshooting needs to be done before we can reach the conclusion you did.

Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson


bluepoint

join:2001-03-24
Without the router
1 2080 ms 1511 ms 1186 ms cpe-24-xxx-xxx-x.nyc.res.rr.com [24.xxx.xxx.x]

With the router
1 4 ms 1 ms 1 ms 192.168.1.1
2 3332 ms 3124 ms 2629 ms cpe-74-xx-xx-x.nyc.res.rr.com [74.xx.xx.x]

From a congestion point of view, they are just the same high ping times, that were taken at different times. His non prime traces is a lot better in single or ten ms digit. Compared to our node, that is not congested even at night and because of it we get the same speed consistently at anytime. Here's the gateway's ping right now.
2. hop: 68.xxx.xxx.x (cpe-68-xxx-xxx-x.NYC.res.rr.com): 20 ms


hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
kudos:11

1 recommendation

Sigh.

Lets look at the last hop

With the router Night:

21 20 ms 22 ms 22 ms lga15s28-in-f3.1e100.net [74.125.226.195]

11 * 14 ms 15 ms 170.149.168.130

With the router Morning:

16 19 ms 21 ms 22 ms lga15s28-in-f5.1e100.net [74.125.226.197]

11 15 ms 15 ms 15 ms 170.149.168.130

Without the router:

10 18 ms 14 ms 15 ms 170.149.168.130

14 20 ms 21 ms 19 ms lga15s34-in-f5.1e100.net [173.194.43.5]

As any technically minded person will tell you the only hop that we care about is the last one. No one is interested in the first one other than you.
As I said previously the packet loss with the router is a concern.

Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson


bluepoint

join:2001-03-24
said by hobgoblin:

Sigh.

As any technically minded person will tell you the only hop that we care about is the last one.

Wrong, a technically knowledgeable person will look at every hop, any congestion at each route will affect the latency. And that's why traceroute helps technical people to find router problems if any.


hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
kudos:11
"Wrong, a technically knowledgeable person will look at every hop, any congestion at each route will affect the latency. "

Ok I am done with this conversation. This discussion has been done to death multiple times over the years. You must have missed them.

Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson


bluepoint

join:2001-03-24
Multiple times dead, wow that's your best technical answer. I agree, I must end this conversation. Don't forget though you need to help the OP.


hobgoblin
Sortof Agoblin
Premium
join:2001-11-25
Orchard Park, NY
kudos:11
"Multiple times dead, wow that's your best technicl answer."

A technical person can always spell technical correctly. I would suggest the OP visits »Time Warner Cable TV/Voice and posts relevant information in that forum.

Good edit!

Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson


bluepoint

join:2001-03-24
said by hobgoblin:

"A technical person can always spell technical correctly. Hob

Nope you're too late.


Beachie
Stranded in paradise

join:2001-07-12
St. Pete, FL
kudos:2
It's not too late to fix [sic] loosing


skuv

@rr.com
reply to bluepoint
said by bluepoint:

Wrong, a technically knowledgeable person will look at every hop, any congestion at each route will affect the latency. And that's why traceroute helps technical people to find router problems if any.

A traceroute directs UDP or ICMP at EACH HOP separately, and gets an ICMP response from EACH HOP separately. Each measurement of latency is for the time which that individual hop responded to the UDP or ICMP from the traceroute.

If I am getting low latency from the last hop, then that is all that matters.

Latency at any particular hop that doesn't continue is latency to the CPU of that particular router hop. Modern day service provider routers have the management plane separated from the forwarding plane. A router responds to traceroutes from its management plane. If that management plane is busy, it will delay the ICMP response to the traceroute. All of the other traceroute packets pass through the router's forwarding plane, which is controlled by ASICs or other dedicated CPUs within the linecards of the router and are designed to forward packets quickly.

Maybe now you'll understand why high latency from a specific hop does not affect the entire round trip if the same latency is not being added to each hop thereafter.

Latency caused by congestion would show up at every hop in the traceroute, because the forwarding plane (the linecards) have the actual ports that would be congested. Adding the congestion latency to each traceroute packet that is being sent to each subsequent packet after the congested port.

This traceroute shows no signs of congestion latency.


Napsterbater
Meh
Premium,MVM
join:2002-12-28
Milledgeville, GA
Reviews:
·Xcelerate Broadb..
·Windstream
reply to bluepoint
said by bluepoint:

said by hobgoblin:

Sigh.

As any technically minded person will tell you the only hop that we care about is the last one.

Wrong, a technically knowledgeable person will look at every hop, any congestion at each route will affect the latency. And that's why traceroute helps technical people to find router problems if any.

In this case there is no evidence of really anything wrong in any of the trace routes except for that fist one with all of the *'s in it.

The "First" hop with high latency just mean the device is putting ICMP directed at it and only at it on the back burner while it deals with other traffic, hence why the rest of the hops have a normal latency, if the high latency continued then yes there really is a delay there.

What ever the problem is its not showing in the traceroute.
--
ASUS M4A79T Deluxe | AMD Phenom II x3 720 BE AM3 w/4 Cores @ 3.41Ghz(OC) | 4Gb DDR3 Memory @ 1600mhz | Sapphire ATI HD4870 1GB 800mhz/1000mhz(OC) | 2x500GB HDD's Raid 0 | Windows 7 Ultimate x64 Build 7600 (RTM) | Windstream DSL 12m (14.9m Sync)/766k


golden eagle
Aquila chrysaetos
Premium
join:2002-08-06
On a cliff
reply to skuv
Whoosh. Okay that being said what could be causing my consistent connection issues? TWC seems to be of little help. As it turns out that "24 hour device watch" is a 14 day watch and short of sending someone out to check my line when I experience the issue - which TW doesn't send techs out at that hour - I may be sol. They told me last night that my "modem is offline" but I was connected to the net. Certain pages did load it just took forever. I mean I understand that as demand grows during the day my speeds will be lower but starting last week and coming to a climax the last two nights nights I've been essentially regulated to an AOL dial-up connection. I couldn't even log in here last night to read thru this thread.

All I know as a novice is that my issue is consistent -every day and there's a pattern to it - in the evenings. I'd like to get more insight so I can understand what the cause is.