traceroute endet bei te3-1.car14.hstntx2.networklayer.com
- Thread starter treebeard
- Start date
Code:
1. firewall.home.local 0.0% 8 0.3 0.2 0.2 0.4 0.1
2. 80-218-208-1.dclient.hispeed.ch 0.0% 8 9.0 9.6 8.3 12.0 1.2
3. 217-168-56-101.static.cablecom.ch 0.0% 8 10.5 9.7 7.5 13.4 2.2
4. 62.2.4.157 0.0% 8 18.9 11.7 7.9 18.9 3.6
5. 84-116-130-225.aorta.net 0.0% 8 131.3 126.2 115.8 167.3 17.3
6. 84-116-130-61.aorta.net 0.0% 8 110.2 111.1 110.1 112.0 0.7
7. us-was03a-rd1-xe-0-0-0.aorta.net 0.0% 8 116.8 124.7 112.1 145.2 12.5
8. us-was03a-ri1-xe-0-1-0.aorta.net 0.0% 8 115.5 117.6 115.3 123.5 2.8
9. dcp-brdr-03.inet.qwest.net 0.0% 8 125.9 122.9 116.1 130.4 5.2
10. dcp-edge-01.inet.qwest.net 0.0% 8 110.6 115.7 110.6 129.7 6.6
11. ae11.bbr02.eq01.wdc02.networklayer.com 0.0% 7 116.4 117.6 115.1 127.3 4.3
12. ae7.bbr01.eq01.wdc02.networklayer.com 0.0% 7 111.8 111.9 110.2 113.0 1.0
13. ae0.bbr01.tl01.atl01.networklayer.com 0.0% 7 124.6 127.2 124.4 134.6 4.3
14. ae13.bbr02.eq01.dal03.networklayer.com 0.0% 7 143.4 145.0 142.9 150.4 2.7
15. ae0.bbr02.sr02.hou02.networklayer.com 0.0% 7 156.0 153.7 149.9 159.1 3.0
16. po32.dsr01.hstntx2.networklayer.com 0.0% 7 152.0 152.9 150.6 162.4 4.2
17. te3-1.car14.hstntx2.networklayer.com 0.0% 7 151.4 151.3 150.3 153.4 1.2
18. e6.70.7bae.static.theplanet.com 0.0% 7 159.6 161.2 157.6 167.4 3.5
Joe User
Zentrum der Macht
Wenn wir einfach mal stumpf davon ausgehen (was man allerdings nicht kann), dass der Traceroute in beide Richtungen den gleichen Weg nimmt, dann möchte QWest sein Netzwerk von Scriptkiddies sauber halten und verwirft deshalb Traceroutes und Pings auf seine Kunden.
Legitimes Mittel gegen dumme Scriptkiddies, erschwert dafür das Debugging unnötig.
Legitimes Mittel gegen dumme Scriptkiddies, erschwert dafür das Debugging unnötig.
Danke für Eure Antworten. Hier ist das traceroute in die andere Richtung:
Code:
traceroute 188.40.112.205
traceroute to 188.40.112.205 (188.40.112.205), 30 hops max, 40 byte packets
1 e1.70.7bae.static.theplanet.com (174.123.112.225) 0.540 ms 0.523 ms 0.555 ms
2 te1-5.dsr02.hstntx2.networklayer.com (74.55.252.221) 0.397 ms 0.444 ms 0.495 ms
3 ae17.bbr02.sr02.hou02.networklayer.com (173.192.18.238) 0.218 ms ae17.bbr01.sr02.hou02.networklayer.com (173.192.18.234) 0.217 ms ae17.bbr02.sr02.hou02.networklayer.com (173.192.18.238) 0.215 ms
4 ae3.bbr01.eq01.dal03.networklayer.com (173.192.18.218) 5.262 ms ae3.bbr02.eq01.dal03.networklayer.com (173.192.18.220) 15.809 ms 15.822 ms
5 ae0.bbr01.eq01.chi01.networklayer.com (173.192.18.137) 32.902 ms 32.899 ms 32.888 ms
6 ae0.bbr02.tl01.nyc01.networklayer.com (173.192.18.133) 102.159 ms ae0.bbr01.eq01.chi01.networklayer.com (173.192.18.137) 35.121 ms ae0.bbr02.tl01.nyc01.networklayer.com (173.192.18.133) 100.249 ms
7 ae0.bbr02.tl01.nyc01.networklayer.com (173.192.18.133) 101.996 ms ae0.bbr01.tg01.lon01.networklayer.com (50.97.18.205) 119.890 ms 119.007 ms
8 ae0.bbr01.tg01.lon01.networklayer.com (50.97.18.205) 120.487 ms ae0.bbr01.xn01.fra01.networklayer.com (50.97.18.209) 135.266 ms ae0.bbr01.tg01.lon01.networklayer.com (50.97.18.205) 124.434 ms
9 decix-gw.hetzner.de (80.81.192.164) 136.593 ms ae0.bbr01.xn01.fra01.networklayer.com (50.97.18.209) 134.687 ms decix-gw.hetzner.de (80.81.192.164) 136.799 ms
10 decix-gw.hetzner.de (80.81.192.164) 133.853 ms 138.721 ms 139.904 ms
11 hos-tr4.ex3k10.rz10.hetzner.de (213.239.227.235) 136.725 ms hos-tr2.ex3k10.rz10.hetzner.de (213.239.227.171) 136.537 ms hos-tr1.ex3k10.rz10.hetzner.de (213.239.227.139) 138.575 ms
12 hos-tr1.ex3k10.rz10.hetzner.de (213.239.227.139) 144.766 ms * hos-tr2.ex3k10.rz10.hetzner.de (213.239.227.171) 139.640 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *