CIX or CRL problems?
I am not able to get past 149.20.0.0 to get to CRL. Is this a problem with CRL or CIX? Does anyone know? owlman.academ.com% traceroute 140.145.0.1 traceroute to 140.145.0.1 (140.145.0.1): 1-30 hops, 38 byte packets 1 ACADEM-ISDN.ACADEM.COM (198.137.249.254) 1.99 ms (ttl=64!) 2.5 ms (ttl=64!) 1.93 ms (ttl=64!) 2 HOU6-E0.SESQUI.NET (128.241.151.86) 68.6 ms (ttl=63!) 24.1 ms (ttl=63!) 23.6 ms (ttl=63!) 3 128.241.151.83 (128.241.151.83) 295 ms 24.6 ms 37.4 ms 4 HOU1-F20.SESQUI.NET (128.241.200.81) 91.4 ms 34.2 ms 43.8 ms 5 MCI-F0.SESQUI.NET (192.67.13.189) 96.8 ms 25.7 ms 36.7 ms 6 border1-hssi1-0.Houston.mci.net (204.70.36.5) 29.5 ms 260 ms 312 ms 7 core1-fddi-0.Houston.mci.net (204.70.2.97) 421 ms 492 ms 146 ms 8 core1-hssi-4.Dallas.mci.net (204.70.1.121) 59.1 ms 108 ms 41.1 ms 9 core3.SanFrancisco.mci.net (204.70.4.17) 75.9 ms 195 ms 75.3 ms 10 mae-west-nap.SanFrancisco.mci.net (204.70.1.14) 98.9 ms 79.5 ms 103 ms 11 T3-CRL-SFO-01-H1/0.US.CRL.NET (198.32.136.10) 87.9 ms 172 ms 185 ms 12 T3-CRL-SFO-01-H3/0.US.CRL.NET (149.20.64.19) 122 ms (ttl=245!) 178 ms (ttl=245!) 215 ms (ttl=245!) 13 * * * 14 * * * 15 * * * .... 30 * * * owlman.academ.com% traceroute 165.113.19.6 traceroute to 165.113.19.6 (165.113.19.6): 1-30 hops, 38 byte packets 1 ACADEM-ISDN.ACADEM.COM (198.137.249.254) 74.6 ms (ttl=64!) 29.1 ms (ttl=64!) 3.8 ms (ttl=64!) 2 HOU6-E0.SESQUI.NET (128.241.151.86) 314 ms (ttl=63!) 93.7 ms (ttl=63!) 216 ms (ttl=63!) 3 128.241.151.83 (128.241.151.83) 130 ms 120 ms 96.2 ms 4 HOU1-F20.SESQUI.NET (128.241.200.81) 202 ms 282 ms 889 ms 5 MCI-F0.SESQUI.NET (192.67.13.189) 206 ms 25.8 ms 25.0 ms 6 border1-hssi1-0.Houston.mci.net (204.70.36.5) 29.5 ms 35.4 ms 36.8 ms 7 core1-fddi-0.Houston.mci.net (204.70.2.97) 81.9 ms 160 ms 233 ms 8 core1-hssi-4.Dallas.mci.net (204.70.1.121) 35.9 ms 193 ms 165 ms 9 core3.SanFrancisco.mci.net (204.70.4.17) 233 ms * 128 ms 10 mae-west-nap.SanFrancisco.mci.net (204.70.1.14) 135 ms 271 ms 311 ms 11 T3-CRL-SFO-01-H1/0.US.CRL.NET (198.32.136.10) 178 ms 114 ms 80.3 ms 12 T3-CRL-SFO-01-H3/0.US.CRL.NET (149.20.64.19) 98.2 ms (ttl=245!) 137 ms (ttl=245!) 255 ms (ttl=245!) 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 T3-CRL-SFO-01-H3/0.US.CRL.NET (149.20.64.19) 116 ms (ttl=245!) !H * *
At 09:39 -0500 7/23/96, Stan Barber wrote:
I am not able to get past 149.20.0.0 to get to CRL. Is this a problem with CRL or CIX? Does anyone know?
I'm seeing 149.20.0.1 dump into Netcom at both Mae-West and the PB NAP. Jim Browne jbrowne@jbrowne.com "Straggle into the station, headed for your destination; But the price you pay to nowhere has increased a dollar more." - Celebration Day/ Led Zeppelin
At 09:53 -0700 7/23/96, Jim Browne wrote:
Allow me to remove foot from mouth. 149.20/16 is dumping into Netcom. 149.20.64/24 is dumping into CRL (& CIX) from my perspectives. (That's what I get for coming into work early.) Jim Browne jbrowne@jbrowne.com "Straggle into the station, headed for your destination; But the price you pay to nowhere has increased a dollar more." - Celebration Day/ Led Zeppelin
crash % traceroute freefall.cdrom.com traceroute to freefall.FreeBSD.org (204.216.27.4), 30 hops max, 40 byte packets 1 core4-e1.hou.neo.net (206.109.4.126) 0.885 ms 0.705 ms 0.666 ms 2 core3-fe2.hou.neo.net (206.109.7.126) 1.323 ms 1.271 ms 1.281 ms 3 core1-fe1-1.hou.neo.net (206.109.7.34) 2.134 ms 2.127 ms 2.181 ms 4 border8-hssi1-0.Houston.mci.net (204.70.195.5) 4.782 ms 4.034 ms 3.551 ms 5 core2-fddi-1.Houston.mci.net (204.70.191.65) 127.672 ms 3.284 ms 204.229 ms 6 core1-aip-4.Houston.mci.net (204.70.1.189) 7.296 ms 4.127 ms 3.511 ms 7 core1-hssi-4.Dallas.mci.net (204.70.1.121) 10.185 ms 10.463 ms 13.329 ms 8 core3.SanFrancisco.mci.net (204.70.4.17) 49.368 ms 52.705 ms 51.384 ms 9 mae-west-nap.SanFrancisco.mci.net (204.70.1.14) 54.612 ms 53.221 ms 55.874 ms 10 T3-CRL-SFO-01-H1/0.US.CRL.NET (198.32.136.10) 78.138 ms 72.259 ms 68.579 ms 11 T3-CRL-SFO-01-H3/0.US.CRL.NET (149.20.64.19) 80.893 ms 82.276 ms 91.322 ms 12 E0-CRL-SFO-02-E0/0.US.CRL.NET (165.113.55.2) 119.768 ms 128.540 ms 138.504 ms 13 T1-CDROM-00-EX.US.CRL.NET (165.113.118.2) 123.243 ms 105.063 ms 85.623 ms 14 freefall.FreeBSD.ORG (204.216.27.4) 107.998 ms 101.339 ms 113.213 ms freefall % traceroute mirror.neosoft.com traceroute mirror.neosoft.com traceroute to mirror.neosoft.com (206.109.1.17), 30 hops max, 40 byte packets 1 gatekeeper.cdrom.com (204.216.27.1) 2.229 ms 2.025 ms 2.817 ms 2 R-CRL-SFO-01-EX.US.CRL.NET (165.113.118.1) 8.155 ms 8.856 ms 25.995 ms 3 (165.113.55.1) 154.320 ms 52.897 ms 301.080 ms 4 border3-hssi1-0.SanFrancisco.mci.net (149.20.64.9) 107.457 ms 93.237 ms 64.428 ms 5 core1-fddi-0.SanFrancisco.mci.net (204.70.2.161) 88.451 ms 89.330 ms * 6 core3.Dallas.mci.net (204.70.4.13) 136.363 ms 106.641 ms 132.381 ms 7 core1-hssi-3.Houston.mci.net (204.70.1.122) 151.463 ms 201.586 ms * 8 core2-aip-4.Houston.mci.net (204.70.1.190) 104.699 ms 144.291 ms 169.130 ms 9 border8-fddi-0.Houston.mci.net (204.70.191.67) 164.093 ms 169.815 ms 86.252 ms 10 neosoft.Houston.mci.net (204.70.195.6) 97.959 ms 87.195 ms 117.670 ms 11 mirror.neosoft.com (206.109.1.17) 100.091 ms 100.151 ms 88.256 ms Seems that CRL and MCI are prefering each others routes at different NAPs? Scott -- smace@neosoft.com - KC5NUA - Scott Mace - Network Engineer - Neosoft Inc. Any opinions expressed are mine.
participants (3)
-
Jim Browne -
Scott Mace -
sob＠academ.com