Hi all.
I have an outside-in reachability problem I can't nail down. If you
have a second, can you email me a traceroute to 207.65.163.1?
Especially if you transit AS1239.
Thanks to all,
Ejay Hire
Ejay.hire@isdn.net
Sprint is a transit supplier of ours, so it could be
jes@jes.noc:/home/jes$ traceroute -P icmp 207.65.163.1
traceroute to 207.65.163.1 (207.65.163.1), 64 hops max, 60 byte
packets
1 singel-gap-1-if2.router.demon.net (194.159.72.242) 1.949 ms
0.819 ms 0.792 ms
2 ams1-access-1-ge-0-1-0-30.router.nl.demon.net (195.173.56.66)
1.604 ms 1.215 ms 1.205 ms
3 nkf-border-1-at-1-2-0-0.router.nl.demon.net (82.161.255.30) 2.681
ms 2.546 ms 2.462 ms
4 ge-2-0-205.ipcolo1.Amsterdam1.Level3.net (212.72.46.85) 2.512 ms
2.284 ms 1.941 ms
5 ae-0-53.mp1.Amsterdam1.Level3.net (213.244.165.65) 2.767 ms
3.071 ms 2.760 ms
6 as-1-0.bbr2.London1.Level3.net (212.187.128.25) 10.547 ms 10.485
ms 10.460 ms
7 as-0-0.bbr1.NewYork1.Level3.net (4.68.128.106) 75.699 ms 75.776
ms 78.550 ms
8 ge-6-0-0-55.gar4.NewYork1.Level3.net (4.68.97.133) 79.350 ms
ge-6-0-0-51.gar4.NewYork1.Level3.net (4.68.97.5) 80.134 ms
ge-6-0-0-55.gar4.NewYork1.Level3.net (4.68.97.133) 80.280 ms
9 uunet-level3-oc48.NewYork1.Level3.net (209.244.160.182) 76.442 ms
76.273 ms 76.399 ms
10 0.so-6-0-0.XL2.NYC4.ALTER.NET (152.63.21.82) 75.807 ms 77.958 ms
75.817 ms
11 0.so-4-0-0.TL2.NYC9.ALTER.NET (152.63.23.129) 76.652 ms 76.566
ms 76.648 ms
12 0.so-7-0-0.TL2.ATL1.ALTER.NET (152.63.10.125) 97.201 ms 95.851
ms 96.715 ms
13 0.so-2-0-0.XL2.ATL1.ALTER.NET (152.63.101.54) 95.898 ms 96.718
ms 96.476 ms
14 0.so-7-0-0.XR2.ATL1.ALTER.NET (152.63.86.102) 95.312 ms 96.045
ms 96.817 ms
15 194.ATM6-0.GW3.ATL1.ALTER.NET (152.63.83.105) 96.062 ms 97.709
ms 95.400 ms
16 bna-cr1b-s1-0.nrep.net (157.130.69.254) 100.555 ms 101.191 ms
100.634 ms
17 nreprtr01.isdn.net (207.65.70.97) 104.918 ms 106.249 ms 107.451
ms
18 nreprtr03.isdn.net (207.65.70.102) 101.798 ms 102.063 ms
105.085 ms
19 host1-163-65-207.aimhealth.com (207.65.163.1) 104.344 ms 104.150
ms 103.762 ms
You can run these on your own at traceroute.org or telnet to route-server.cerf.net
C:\>tracert 207.65.163.1
Tracing route to host1-163-65-207.aimhealth.com [207.65.163.1]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms my network
2 <10 ms <10 ms <10 ms my network
3 <10 ms <10 ms <10 ms my network
4 <10 ms 15 ms <10ms my network
5 16 ms <10 ms 15 ms so0-0-0-2488m.ar1.dal2.gblx.net [67.17.73.30]
6 <10 ms 15 ms <10 ms 208.51.134.18
7 <10 ms 15 ms <10 ms 0.so-1-3-0.XL1.DFW9.ALTER.NET [152.63.99.210]
8 16 ms 15 ms 16 ms 0.so-0-0-0.TL1.DFW9.ALTER.NET [152.63.0.193]
9 16 ms 31 ms 31 ms 0.so-0-0-0.TL1.ATL1.ALTER.NET [152.63.101.57]
10 16 ms 31 ms 31 ms 0.so-1-3-0.XL1.ATL1.ALTER.NET [152.63.87.29]
11 15 ms 32 ms 31 ms 0.so-7-0-0.XR1.ATL1.ALTER.NET [152.63.86.86]
12 15 ms 31 ms 32 ms 195.ATM7-0.GW3.ATL1.ALTER.NET [152.63.83.101]
13 47 ms 47 ms 47 ms bna-cr1b-s1-0.nrep.net [157.130.69.254]
14 32 ms 31 ms 31 ms nreprtr01.isdn.net [207.65.70.97]
15 31 ms 47 ms 31 ms nreprtr03.isdn.net [207.65.70.102]
16 47 ms 31 ms 32 ms host1-163-65-207.aimhealth.com [207.65.163.1]
Trace complete.
C:\>
You can run these on your own at traceroute.org or telnet to
route-server.cerf.net
'cept they don't fail
ejay was lookin' for the failure case(s), e.g. one of my exits
root@psg1> traceroute 207.65.163.1
traceroute to 207.65.163.1 (207.65.163.1), 30 hops max, 40 byte packets
1 ge3-0.cr02.sea01.pccwbtn.net (198.32.180.13) 1.026 ms 0.843 ms 0.715 ms
2 ge2-1.br01.sjo01.pccwbtn.net (63.218.6.130) 18.876 ms 18.913 ms 19.095 ms
3 webusenet.ge3-5.2.br01.sjo01.pccwbtn.net (63.218.7.126) 20.341 ms 18.915 ms 19.744 ms
4 63.223.20.45 (63.223.20.45) 19.605 ms 19.557 ms 19.841 ms
5 b0-00.lax.ge1-36-1.wvfiber.net (63.223.0.178) 27.823 ms 27.699 ms 28.160 ms
6 b0-00.dal.pos1-16-1.wvfiber.net (63.223.0.73) 92.641 ms 92.877 ms 93.555 ms
7 63.223.0.69 (63.223.0.69) 92.423 ms 92.341 ms 92.570 ms
8 e00.nsh.pos2-0.wvfiber.net (63.223.0.234) 97.077 ms 96.867 ms 96.901 ms
9 unknown63223008166.ibis7.net (63.223.8.166) 98.379 ms 98.476 ms 98.620 ms
10 host209-122-65-207.isdn.net (207.65.122.209) 99.757 ms 98.150 ms 98.576 ms
11 nreprtr03.isdn.net (207.65.70.102) 98.672 ms 98.762 ms 108.476 ms
12 * * *
13 * * *
14 * * *
15 * * *
randy
Thanks to all who replied.
It's obviously not a reachability problem in getting to this
address, and looking in the other direction I figured it
out.
Both of the customers having the problem are coming from
71.96/16, and they both stop at
4 56 ms 55 ms 55 ms ge3-0.5.cr01.lax04.pccwbtn.net
[63.218.51.29]
With 71/9 only allocated last august, I think I'm hitting a
bogon filter on the other side of the link. I'll call
pccwbtn.net.
Again, thanks for the help.
Ejay Hire
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]
On
Behalf Of Ejay Hire
Sent: Tuesday, March 15, 2005 11:27 AM
To: nanog@merit.edu
Subject: Traceroute to 207.65.163.1Hi all.
I have an outside-in reachability problem I can't nail
down. If you
have a second, can you email me a traceroute to
207.65.163.1?