how-to block ads
|
|
Share Topic
 |
 |
|
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | reply to funchords
Re: Comcast is using Sandvine to manage P2P Connectionssaid by funchords:WHERE: On the boundaries, at the point where Comcast connects to other points of the Internet, I'm going to have to modify this, as I'm now seeing RSTs being forged on paths that never leave Comcast.net space.
Comcast techies -- can you help me understand why? Also, is there a decoder ring for the prefixes "GE," "TE," "PO," and etc.?
Tracing route to c-68-50-221-XXX.hsd1.md.comcast.net [68.50.221.XXX]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.177.251
2 * * * Request timed out.
3 180 ms 66 ms 21 ms GE-1-11-ur03.beaverton.or.bverton.comcast.net [68.87.218.89]
4 12 ms 21 ms 41 ms te-9-2-ar01.beaverton.or.bverton.comcast.net [68.87.216.29]
5 * 24 ms * po-10-ar01.troutdale.or.bverton.comcast.net [68.87.216.14]
6 69 ms 47 ms 26 ms te-6-1-cr01.seattle.wa.cbone.comcast.net [68.86.72.73]
7 99 ms 122 ms 88 ms te-1-1-cr01.ogden.ut.cbone.comcast.net [68.86.68.49]
8 250 ms 91 ms 59 ms te-1-1-cr01.denver.co.cbone.comcast.net [68.86.68.45]
9 126 ms 66 ms 139 ms te-1-1-cr01.omaha.ne.cbone.comcast.net [68.86.68.41]
10 81 ms 88 ms 105 ms te-1-1-cr01.chicago.il.cbone.comcast.net [68.86.68.29]
11 79 ms 155 ms 80 ms te-1-1-cr01.cleveland.oh.cbone.comcast.net [68.86.68.21]
12 109 ms 100 ms 215 ms te-1-1-cr01.pittsburgh.pa.cbone.comcast.net [68.86.68.118]
13 84 ms 165 ms 150 ms te-1-1-cr02.pittsburgh.pa.cbone.comcast.net [68.86.68.122]
14 189 ms 256 ms 95 ms te-2-1-cr01.mclean.va.cbone.comcast.net [68.86.68.126]
15 93 ms 168 ms 160 ms te-9-4-ar01.capitolhghts.md.bad.comcast.net [68.86.72.2]
16 323 ms 151 ms 284 ms po-90-ar01.manassascc.va.bad.comcast.net [68.87.129.81]
17 238 ms 129 ms 120 ms po-10-ar01.howardcounty.md.bad.comcast.net [68.87.129.29]
18 103 ms 103 ms 103 ms te-9-2-ur03.rockville.md.bad.comcast.net [68.87.136.6]
19 106 ms 155 ms 119 ms te-9-2-ur02.rockville.md.bad.comcast.net [68.87.129.157]
20 109 ms 130 ms 107 ms ge-5-42-ur01.rockville.md.bad.comcast.net [68.87.136.53]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
--
Robb Topolski -= funchords.com =- Hillsboro, Oregon USA
Are you affected by Comcast's RST forging? How to test it! -or- Read my original report. | | |
|
 EGThe wings of lovePremium
join:2006-11-18
Union, NJ
kudos:9
4 edits | said by funchords:Comcast techies -- can you help me understand why? Also, is there a decoder ring for the prefixes "GE," "TE," "PO," and etc.? ge = gigabit ethernet.
te = ten gigabit ethernet.
p, po, pos = Packet Over Sonet (an OC-3 or faster connection).
1-1, 1-2, 1-11, 6-1, 9-1, 2-2, etc. = slot and port.
ar01, cr01, ur01 = probably a router name ?
--
Let us never forget 9/11 | |
1 edit | said by EG 
ge = gigabit ethernet.
te = ten gigabit ethernet.
p, po, pos = Packet Over Sonet (an OC-3 or faster connection).
1-1, 1-2, 1-11, 6-1, 9-1, 2-2, etc. = slot and port.
ar01, cr01, ur01 = probably a router name ?
:
Judging by the location of these names - 'cr' appearing on everything with a 'cbone' hostname for example - it would appear that these are as follows: 'cr' is a core router, or a backbone router. 'ar' would be an access router, something in a local metro region. 'ur' could be a user router, or perhaps more likely it is named after the uBR router series from Cisco (uBR means universal Broadband Router) widely used in cable internet operations. | |
EGThe wings of lovePremium
join:2006-11-18
Union, NJ
kudos:9 | Thanks for expanding  | |
|
