[Coco] Gene's Web Page

[Johann Klasek]

On Mon, Sep 02, 2013 at 08:55:18PM -0500, Michael Graham wrote:
> 
> >For the curious, the last hop should look something like this:
> >
> >traceroute to coyoteden.dyndns-free.com (204.111.64.149), 30 hops max, 60
> >byte packets
> >  1  n64s149.fttx.shentel.net (204.111.64.149)  0.248 ms  0.325 ms  0.419 
> >  ms
> >
> >I see it is also responding to a ping, which it shouldn't be. The ping
> >filter is on.
> >
> >Can you folks ping it from your locations?
> 
> I'm not able to ping it from here.

Because ICMP pings are blocked or filtered, traceroute tools based on
UDP+ICMP do not provide any usable information on the last hop. To use
tcptraceroute maybe the better way:

tcptraceroute coyoteden.dyndns-free.com 85
Tracing the path to coyoteden.dyndns-free.com (204.111.64.149) on TCP port 85, 30 hops max
[..]
 5  vlan713.wien1.aco.net (193.171.13.9)  0.482 ms  0.462 ms *
 6  vlan71.wien21.aco.net (193.171.23.18)  0.755 ms  0.687 ms  0.668 ms
 7  bundle-ether-21-73.core21.aco.net (193.171.23.42)  1.496 ms  1.054 ms  0.921 ms
 8  212.73.203.17  0.603 ms  0.684 ms  0.726 ms
 9  ae-0-11.bar1.Vienna1.Level3.net (4.69.153.149)  8.115 ms  0.854 ms  0.908 ms
10  ae-12-12.ebr2.Frankfurt1.Level3.net (4.69.153.146)  12.326 ms  13.368 ms  12.355 ms
11  ae-63-63.csw1.Frankfurt1.Level3.net (4.69.163.2)  12.438 ms  12.330 ms  12.367 ms
12  * * *
13  xe-0-4-0-7.r02.frnkge03.de.bb.gin.ntt.net (129.250.8.205)  12.957 ms  12.914 ms  12.934 ms
14  ae-2.r20.frnkge04.de.bb.gin.ntt.net (129.250.5.217)  13.045 ms  13.067 ms  13.616 ms
15  ae-1.r21.asbnva02.us.bb.gin.ntt.net (129.250.3.20)  99.076 ms  113.021 ms  99.202 ms
16  ae-2.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.114)  100.150 ms  100.168 ms  100.077 ms
17  xe-0-1-0-9.r00.asbnva02.us.ce.gin.ntt.net (168.143.97.178)  99.845 ms  99.689 ms  99.835 ms
18  * * *
19  * * n64s149.fttx.shentel.net (204.111.64.149) [closed] 1507.610 ms

"closed" means that the port responds with TCP RST, hence is reachable.

I suspect the router is answering and does not correctly handle the port
forwarding (as already mentioned). Any other port show nearly the same
trace ... for example 5013:

[..]
17  xe-0-1-0-9.r00.asbnva02.us.ce.gin.ntt.net (168.143.97.178)  106.726 ms  106.764 ms  106.758 ms
18  * * *
19  * * *
20  * * n64s149.fttx.shentel.net (204.111.64.149) [closed] 878.924 ms



Johann