Also ich hab jetzt mal die website per name gepingt, direkt nachdem ich erst drauf war, dann aber beim Kommentar verfassen plötzlich nichts mehr ging.
Ergebnis: PING
www.facebook.com (243.185.187.39): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
usw. usw.
D.h. die Pakete kommen nicht an, ne?
Der Test mit der IP dagegen fällt besser aus:
PING 69.63.189.21 (69.63.189.21): 56 data bytes
64 bytes from 69.63.189.21: icmp_seq=0 ttl=244 time=103.622 ms
64 bytes from 69.63.189.21: icmp_seq=1 ttl=244 time=101.849 ms
64 bytes from 69.63.189.21: icmp_seq=2 ttl=244 time=102.266 ms
64 bytes from 69.63.189.21: icmp_seq=3 ttl=244 time=101.605 ms
64 bytes from 69.63.189.21: icmp_seq=4 ttl=244 time=103.271 ms
64 bytes from 69.63.189.21: icmp_seq=5 ttl=244 time=102.233 ms
64 bytes from 69.63.189.21: icmp_seq=6 ttl=244 time=103.609 ms
64 bytes from 69.63.189.21: icmp_seq=7 ttl=244 time=103.862 ms
64 bytes from 69.63.189.21: icmp_seq=8 ttl=244 time=102.744 ms
64 bytes from 69.63.189.21: icmp_seq=9 ttl=244 time=102.889 ms
64 bytes from 69.63.189.21: icmp_seq=10 ttl=244 time=104.268 ms
Sieht ganz so aus, als wenn dann die Verbindung klappt.
Traceroute bringt folgendes zurück:
traceroute to
www.facebook.com (59.24.3.173), 64 hops max, 52 byte packets
1 localhost (192.168.2.1) 3.545 ms 1.485 ms 1.568 ms
2 217.0.117.7 (217.0.117.7) 9.180 ms 9.097 ms 12.745 ms
3 217.0.81.22 (217.0.81.22) 10.778 ms 11.068 ms 10.399 ms
4 f-ea5-i.f.de.net.dtag.de (62.154.16.161) 11.891 ms 12.959 ms 11.835 ms
5 te-4-4.car2.frankfurt1.level3.net (4.68.110.253) 17.770 ms 16.785 ms 15.568 ms
6 vlan99.csw4.frankfurt1.level3.net (4.68.23.254) 27.440 ms 25.337 ms 17.992 ms
7 ae-92-92.ebr2.frankfurt1.level3.net (4.69.140.29) 16.321 ms 16.487 ms 15.833 ms
8 ae-44-44.ebr2.washington1.level3.net (4.69.137.62) 189.063 ms
ae-43-43.ebr2.washington1.level3.net (4.69.137.58) 183.465 ms
ae-41-41.ebr2.washington1.level3.net (4.69.137.50) 186.642 ms
9 ae-62-62.csw1.washington1.level3.net (4.69.134.146) 182.453 ms
ae-82-82.csw3.washington1.level3.net (4.69.134.154) 172.744 ms
ae-72-72.csw2.washington1.level3.net (4.69.134.150) 182.519 ms
10 ae-94-94.ebr4.washington1.level3.net (4.69.134.189) 172.372 ms
ae-74-74.ebr4.washington1.level3.net (4.69.134.181) 194.777 ms 186.897 ms
11 ae-3-3.ebr1.newyork1.level3.net (4.69.132.94) 173.109 ms 188.272 ms 210.404 ms
12 ae-91-91.csw4.newyork1.level3.net (4.69.134.78) 198.344 ms 195.730 ms 177.894 ms
13 ae-94-94.ebr4.newyork1.level3.net (4.69.134.125) 171.546 ms
ae-74-74.ebr4.newyork1.level3.net (4.69.134.117) 184.279 ms
ae-84-84.ebr4.newyork1.level3.net (4.69.134.121) 180.119 ms
14 ae-2.ebr4.sanjose1.level3.net (4.69.135.185) 173.734 ms 174.680 ms 180.294 ms
15 ae-74-74.csw2.sanjose1.level3.net (4.69.134.246) 185.801 ms 186.670 ms 180.175 ms
16 ae-2-79.edge4.sanjose1.level3.net (4.68.18.83) 173.554 ms 171.958 ms
ae-3-89.edge4.sanjose1.level3.net (4.68.18.147) 171.097 ms
17 kt-corporat.edge4.sanjose1.level3.net (4.53.26.2) 172.439 ms 189.187 ms 174.637 ms
18 121.189.1.17 (121.189.1.17) 301.495 ms 300.514 ms 299.136 ms
19 59.18.63.9 (59.18.63.9) 312.401 ms 311.484 ms 314.666 ms
20 59.18.62.98 (59.18.62.98) 311.055 ms 312.095 ms 312.612 ms
21 112.174.56.130 (112.174.56.130) 330.910 ms 330.193 ms 343.787 ms
22 112.190.175.86 (112.190.175.86) 316.607 ms 331.209 ms 318.454 ms
23 112.190.135.154 (112.190.135.154) 332.410 ms 330.853 ms 330.593 ms
24 112.190.136.158 (112.190.136.158) 339.990 ms 316.309 ms 331.819 ms
25 * * *
26 * * *
27 * * *
Was schließt du daraus nun Bananenbieger?