Dotaz: Jak nastavit alternativni cestu k serveru

[pasmen]

Ahoj,
mam nasledujici problem. Potrebuji ziskat data z jisteho serveru, cestu k nemu jsem zjistil pomoci traceroute:

$ traceroute master3.idsoftware.com
traceroute to monster.idsoftware.com (192.246.40.56), 30 hops max, 38 byte packets
 1  SpeedTouch.example.org (10.0.0.138)  1.098 ms  0.678 ms  0.636 ms
 2  80.188.61.141 (80.188.61.141)  10.369 ms  11.088 ms  11.254 ms
 3  80.188.61.129 (80.188.61.129)  11.413 ms  11.033 ms  11.487 ms
 4  80.188.33.245 (80.188.33.245)  11.424 ms  12.486 ms  11.051 ms
 5  80.188.33.245 (80.188.33.245)  11.003 ms  12.454 ms  11.040 ms
 6  194.228.176.253 (194.228.176.253)  12.157 ms  10.491 ms  11.792 ms
 7  p4-0-1-0.r01.frnkge03.de.bb.verio.net (129.250.11.113)  18.805 ms  17.728 ms  17.398 ms
 8  p16-3-0-0.r00.frnkge03.de.bb.verio.net (129.250.2.141)  18.832 ms ge-0-0-0.r01.frnkge02.de.bb.verio.net (129.250.5.38)  19.547 ms p16-3-0-0.r00.frnkge03.de.bb.verio.net (129.250.2.141)  19.180 ms
 9  p16-2-0-0.r00.frnkge02.de.bb.verio.net (129.250.3.194)  22.052 ms  21.402 ms ge-0-0-0.r00.frnkge02.de.bb.verio.net (129.250.5.28)  18.082 ms
10  p16-7-1-2.r20.londen03.uk.bb.verio.net (129.250.5.64)  33.628 ms  33.461 ms  34.722 ms
11  bcr1-ge-4-3-0.Londonlnx.savvis.net (195.66.224.39)  37.827 ms  37.182 ms  36.939 ms
12  bcs1-so-1-1-0.Londonlnx.savvis.net (204.70.193.114)  38.247 ms  36.419 ms  35.908 ms
13  bcs2-so-0-0-0.NewYork.savvis.net (204.70.192.121)  106.336 ms  106.693 ms  105.414 ms
14  bcs2-so-4-0-0.Washington.savvis.net (204.70.192.1)  112.495 ms  110.720 ms  111.446 ms
15  dcr2-so-7-2-0.Atlanta.savvis.net (204.70.192.57)  144.327 ms  143.949 ms  151.411 ms
16  bcs2-so-2-0-0.Dallas.savvis.net (204.70.192.70)  146.521 ms  143.844 ms  143.801 ms
17  bcs1-so-6-0-0.Dallas.savvis.net (204.70.192.49)  142.028 ms  141.419 ms  142.349 ms
18  bcr1-so-0-0-0-500.Dallas.savvis.net (204.70.193.9)  148.197 ms  143.140 ms  142.395 ms
19  idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178)  146.700 ms  148.104 ms  158.634 ms
20  monster.idsoftware.com (192.246.40.56)  273.357 ms  146.090 ms  148.516 ms

Kdyz se ale pokusim ten server pingnout, nemuzu se az k hostu dostat, protoze predposledni server blokuje provoz:

$ ping -c 10 master3.idsoftware.com
PING monster.idsoftware.com (192.246.40.56) 56(84) bytes of data.
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=1 Packet filtered
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=3 Packet filtered
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=4 Packet filtered
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=7 Packet filtered
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=9 Packet filtered
From idsoft-1.CR-1.usdlls.savvis.net (209.176.32.178) icmp_seq=10 Packet filtered

--- monster.idsoftware.com ping statistics ---
10 packets transmitted, 0 received, +6 errors, 100% packet loss, time 8999ms

Takze otazka zni, jde k tomu serveru zvolit nejakou jinou cestu, ktera by nebyla blokovana? Dik

Odpovědi

[Petr Šobáň]

No tak z něho stahuj data co ti brání ?

To že je zablokován ping nic neznamená je to asi zase nějaká nová móda asi od M$.