dear cox

Aug 20, 2009 15:19

This is NOT an acceptable traceroute table ( Read more... )

Leave a comment

Comments 8

genxcub August 20 2009, 22:39:07 UTC
At least your firewall isn't doing too badly for latency. I hate when that happens because it can be such a necessary evil. I'm wondering why there are 3 hops on the same subnet at cox. Is it logging your data?

Reply

redbeardedblond August 20 2009, 22:46:59 UTC
More than likely it's a switch/router or border router/router/switch handoff at a main node.

It's the * * * at hop after hop that's unacceptable. Routes are timing out and that's within their own, main network.

If I thought I could actually talk to a person I'd call and say, "Are you having a DoS or some other incident that you're trying to protect against or are you just sucking?"

Reply

genxcub August 20 2009, 22:50:57 UTC
That last 27 MS may be the hint. Do you have a TTL value on your home router (or on theirs) that may be dropping packets, since that first * * * hop is most likely taking it to the over 100ms mark?

Reply

genxcub August 20 2009, 22:52:48 UTC

squirreltot August 20 2009, 23:19:14 UTC
Hmm, this is not where I thought this post was going...dang!

Rock on Binar Zero One! (OK, maybe I'm a little jealous).

Reply

redbeardedblond August 20 2009, 23:21:03 UTC
Awww... did you want "traceroute table" to mean something in a dungeon? *wink*

Reply

squirreltot August 21 2009, 00:13:04 UTC
OK! All I really saw, immediately, was Dear Cox. And I was thinking that it would lead to a thought provoking photo-essay. The text reminded me of those all ascii files from alt.news.... that had to be compiled. Imagine my surprise when I compiled that text and got a picture of a malibu barbie. Hmmm... kinky.

Reply


Leave a comment

Up