{"id":734,"date":"2004-05-26T09:52:08","date_gmt":"2004-05-26T16:52:08","guid":{"rendered":""},"modified":"2018-11-19T16:39:30","modified_gmt":"2018-11-20T00:39:30","slug":"my-case-against-comcast","status":"publish","type":"post","link":"https:\/\/arcanius.silverfir.net\/blog\/my-case-against-comcast\/","title":{"rendered":"My case against Comcast"},"content":{"rendered":"

\u00a0Bad Comcast<\/p>\n

\u00a0Good Comcast<\/p>\n

Seen above are the same portion of two screen captures from two different games of Counterstrike. The info seen is the output of the function net_graph in the half life engine. As is normal, green means good, and red means bad. In fact, each red mark indicates a lost packet or a period of lost packets. Notice how many red marks there are in the Bad Comcast picture. Of course, that information is very anecdotal and doesn’t really isolate the problem – with just that information, you wouldn’t know if the problem were the counterstrike server, my router, my computer, the wireless link between them, or anything else. So I decided to roll in the big guns: the ping test.<\/p>\n

I used the following command in four seperate command prompt windows:
\nping -t -w 200 host<\/i>
\nwhere
\n-t tells ping to ping until I tell it to stop
\n-w 200 tells ping to stop waiting at 200 ms and
\nhost<\/i> is either an IP adress or a hostname<\/p>\n

Here are the results (grabbed by using control-break and copy\/paste):<\/p>\n

Ping statistics for 192.168.10.200: a computer on the same subnet, just one switch and two cat 5 cables away<\/i>
\nPackets: Sent = 355, Received = 355, Lost = 0 (0% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 0ms, Maximum = 0ms, Average = 0ms<\/p>\n

Ping statistics for 192.168.10.1: this is my router<\/i>
\nPackets: Sent = 1239, Received = 1175, Lost = 64 (5% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 2ms, Maximum = 49ms, Average = 3ms<\/p>\n

Ok, so 5% loss is not ideal and I will try to make that better. I think I could get this to 0% with a little tweaking, but 5% packet loss hardly affects real world performace.<\/p>\n

Ping statistics for 192.168.100.1: this is my cable modem<\/i>
\nPackets: Sent = 1017, Received = 947, Lost = 70 (6% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 4ms, Maximum = 31ms, Average = 5ms<\/p>\n

This is on par with the 5% seen for the router, but the test started later and there are more lost packets, so there are definitely some packets lost between the router and the cable modem… how this is possible escapes me, since they are all of a foot apart with a nice cat5 cable in between. But still, 6% loss is not very noticeable in the real world.<\/p>\n

Now it gets interesting:
\nPing statistics for 24.18.144.1: this is my router’s default gateway<\/i>
\nPackets: Sent = 1230, Received = 864, Lost = 366 (29% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 10ms, Maximum = 480ms, Average = 63ms<\/p>\n

All of my packets have to go through the default gateway, as this is my only path to the internet. And from here to there and back again (without touching the internet along the way), I loose almost 30% of my packets. This is all after my router, mind you, I have no control over anything at this point.<\/p>\n

Now, for the real world test:
\nPing statistics for 216.239.57.99: this is google.com<\/i>
\nPackets: Sent = 1480, Received = 872, Lost = 608 (41% loss),
\nApproximate round trip times in milli-seconds:
\nMinimum = 31ms, Maximum = 489ms, Average = 84ms<\/p>\n

Once we get out into the wild, nearly half of my packets never find their way home. And this is with no load whatsoever on the system.<\/p>\n

“Pour sore misery down on me…” (I’m only happy when it rains)<\/p>\n","protected":false},"excerpt":{"rendered":"

\u00a0Bad Comcast \u00a0Good Comcast Seen above are the same portion of two screen captures from two different games of Counterstrike. The info seen is the output of the function net_graph in the half life engine. As is normal, green means good, and red means bad. In fact, each red mark indicates a lost packet or […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[12,8],"class_list":["post-734","post","type-post","status-publish","format-standard","hentry","category-everything","tag-silverfir","tag-technology"],"_links":{"self":[{"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/posts\/734","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/comments?post=734"}],"version-history":[{"count":2,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/posts\/734\/revisions"}],"predecessor-version":[{"id":2296,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/posts\/734\/revisions\/2296"}],"wp:attachment":[{"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/media?parent=734"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/categories?post=734"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/arcanius.silverfir.net\/blog\/wp-json\/wp\/v2\/tags?post=734"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}