[k1ng]

versuch clara.seilen.de

http://serverfault.com/questions/397...a-ping-attempt

[hanspeter]

Hi Leute,

seit heute morgen um 11 Uhr kann ich mich nicht mehr zum Seilen IRC via SSL Verbinden. Davor ging es ohne Probleme. Jetzt bekomme ich beim Connecten die Meldung IRC connection timed out.
Beim Ping sagt er immer TTL expired in transit. Was hat dies zu bedeuten und wie bekomme ich das hin das ich wieder connecten kann? Liegt es evtl. an OVH selbst?

Was bedeutet dies?

============

Pinging google.de [209.85.229.99] with 32 bytes of data:

Reply from 209.85.229.99: bytes=32 time=18ms TTL=56
Reply from 209.85.229.99: bytes=32 time=19ms TTL=56
Reply from 209.85.229.99: bytes=32 time=18ms TTL=56
Reply from 209.85.229.99: bytes=32 time=19ms TTL=56

Ping statistics for 209.85.229.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms

============

Pinging irc.seilen.de [84.16.231.52] with 32 bytes of data:

Reply from 188.165.9.133: TTL expired in transit.
Reply from 188.165.9.133: TTL expired in transit.
Reply from 188.165.9.133: TTL expired in transit.
Reply from 188.165.9.133: TTL expired in transit.

Ping statistics for 84.16.231.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

============

Tracing route to irc.seilen.de [84.16.231.52]
over a maximum of 30 hops:

1 67 ms * <1 ms 94.23.230.254
2 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
3 2 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
4 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
5 2 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
6 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
7 10 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
8 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
9 <1 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
10 2 ms 1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
11 <1 ms * 1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
12 <1 ms <1 ms 1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
13 <1 ms * 36 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
14 1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
15 <1 ms * * vss-2-6k.routers.chtix.eu [188.165.9.132]
16 1 ms <1 ms 1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
17 3 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
18 <1 ms <1 ms 3 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
19 * <1 ms * vss-2-6k.routers.chtix.eu [188.165.9.132]
20 <1 ms 1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
21 <1 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
22 1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
23 * 1 ms * vss-2-6k.routers.chtix.eu [188.165.9.132]
24 6 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
25 <1 ms * * vss-2-6k.routers.chtix.eu [188.165.9.132]
26 2 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
27 <1 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
28 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]
29 <1 ms * <1 ms vss-2-6k.routers.chtix.eu [188.165.9.132]
30 <1 ms <1 ms <1 ms rbx-99-6k.routers.chtix.eu [188.165.9.133]

Trace complete.

============