[nycbug-talk] Researching ISP for an IP

[Kevin Reiter]

Francisco Reyes wrote:
> On Sun, 14 Aug 2005, George R. wrote:
> 
>> Optonline very infrequently changes it's dynamic clients from what
>> i've seen. And there are enough home routers out there that do not
>> reply to pings. . .
> 
> 
> Not responding to ping I understand.. but shouldn't a traceroute or mtr
> show at least the route up to that machine?
> 
> That's what surprised me the most.

root at perseus [~]# traceroute 167.206.75.27
traceroute to 167.206.75.27 (167.206.75.27), 64 hops max, 44 byte packets
 1  192.168.0.1 (192.168.0.1)  0.306 ms  0.286 ms  0.222 ms
 2  * * *
 3  dstswr2-vlan2.rh.okldnj.cv.net (67.83.248.162)  9.109 ms  8.664 ms
10.513 ms
 4  r4-ge9-0.mhe.prnynj.cv.net (67.83.248.133)  8.353 ms  9.526 ms  9.047 ms
 5  r2-srp3-0.wan.prnynj.cv.net (65.19.112.130)  9.752 ms  8.599 ms  8.953 ms
 6  r1-srp3-0.wan.hcvlny.cv.net (65.19.96.1)  12.800 ms  12.378 ms  12.513 ms
 7  r2-srp5-0.cst.hcvlny.cv.net (65.19.104.4)  11.171 ms  10.786 ms  11.297 ms
 8  65.19.104.33 (65.19.104.33)  13.385 ms  12.966 ms  10.080 ms
 9  r4-ge-1-0-0.cst.hcvlny.cv.net (65.19.105.134)  11.088 ms  15.148 ms
10.605 ms
10  central-state.cst.lightpath.net (167.206.107.34)  15.359 ms  18.217 ms
 17.193 ms
11  ros75-27.optonline.net (167.206.75.27)  17.405 ms  15.383 ms  18.385 ms

root at perseus [~]# ping -c 4 167.206.75.27
PING 167.206.75.27 (167.206.75.27): 56 data bytes
64 bytes from 167.206.75.27: icmp_seq=0 ttl=245 time=15.993 ms
64 bytes from 167.206.75.27: icmp_seq=1 ttl=245 time=15.218 ms
64 bytes from 167.206.75.27: icmp_seq=2 ttl=245 time=20.247 ms
64 bytes from 167.206.75.27: icmp_seq=3 ttl=245 time=15.224 ms

--- 167.206.75.27 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 15.218/16.671/20.247/2.089 ms