Re: styk GTS-ICM - Grupy dyskusyjne w eGospodarka.pl

eGospodarka.pl › Grupy › pl.internet.polip › styk GTS-ICM › Re: styk GTS-ICM

Path: news-archive.icm.edu.pl!newsfeed.gazeta.pl!opal.futuro.pl!news.tvk.wroc.pl!not-
for-mail
From: Admin TVK Tel-Ka <a...@t...wroc.pl.invalid>
Newsgroups: pl.internet.polip
Subject: Re: styk GTS-ICM
Date: Mon, 20 Sep 2004 15:00:30 +0000 (UTC)
Organization: Telewizja Kablowa Wroclaw -- http://www.tvk.wroc.pl/
Lines: 50
Message-ID: <s...@p...tvk.wroc.pl>
References: <cimnbo$ph2$1@atlantis.news.tpi.pl>
NNTP-Posting-Host: 195.140.236.254
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
X-Trace: pyro.tvk.wroc.pl 1095692430 14863 195.140.236.254 (20 Sep 2004 15:00:30 GMT)
X-Complaints-To: a...@t...wroc.pl
NNTP-Posting-Date: Mon, 20 Sep 2004 15:00:30 +0000 (UTC)
User-Agent: slrn/0.9.7.4 (Linux)
Xref: news-archive.icm.edu.pl pl.internet.polip:68289
[ ukryj nagłówki ]
W artykule <cimnbo$ph2$1@atlantis.news.tpi.pl> Jozef Zawislak napisał(a):
>
> Czy ktos wie, co tam sie dzieje?
>
> traceroute to sunsite.icm.edu.pl (193.219.28.2), 30 hops max, 40 byte
> packets
[..]
> icm-s2-213-135-50-41.rtr.net.icm.edu.pl (213.135.50.41) 367.425 ms
> icm-s2-213-135-50-33.rtr.net.icm.edu.pl (213.135.50.33) 195.778 ms
> 6 SunSITE.icm.edu.pl (193.219.28.2) 292.300 ms 432.429 ms 470.705 ms
>

$ traceroute sunsite.icm.edu.pl
traceroute to sunsite.icm.edu.pl (193.219.28.2), 64 hops max, 40 byte packets
1 multiplexer-v1004.core.tvk.wroc.pl (195.140.238.254) 0 ms 0 ms 0 ms
2 AS29512-e3.tvk.wroc.pl (195.140.239.250) 1 ms 0 ms 0 ms
3 do-gts.tvk.wroc.pl (217.153.188.169) 1 ms 4 ms 9 ms
4 taro-poznan-g0-3-0-42.ipartners.pl (217.153.2.213) 6 ms 7 ms 6 ms
5 taro-wawa-as0-0.ipartners.pl (217.153.3.145) 15 ms 18 ms 15 ms
6 taro2-f0-0-220.ipartners.pl (217.153.3.2) 18 ms 13 ms 13 ms
7 icm-r1-193-219-28-233.rtr.net.icm.edu.pl (193.219.28.233) 18 ms 22 ms 21ms
8 icm-s2-213-135-50-41.rtr.net.icm.edu.pl (213.135.50.41) 31 ms
icm-s2-213-135-50-33.rtr.net.icm.edu.pl (213.135.50.33) 21 ms
icm-s2-213-135-50-37.rtr.net.icm.edu.pl (213.135.50.37) 19 ms
9 sunsite.icm.edu.pl (193.219.28.2) 15 ms 20 ms 20 ms
>
> traceroute to dns.atman.pl (217.17.34.10), 30 hops max, 40 byte packets
> 1 157.25.5.193 (157.25.5.193) 9.078 ms 9.856 ms 9.939 ms
> 2 taro7-a3-0-0-32 (217.153.3.149) 58.432 ms 36.783 ms 35.891 ms
[..]
> 7 dns.atman.pl (217.17.34.10) 109.264 ms * 127.836 ms
>
>
> Tak juz dobre pare dni...
>
$ traceroute dns.atman.pl
traceroute to dns.atman.pl (217.17.34.10), 64 hops max, 40 byte packets
1 multiplexer-v1004.core.tvk.wroc.pl (195.140.238.254) 0 ms 0 ms 0 ms
2 AS29512-e3.tvk.wroc.pl (195.140.239.250) 1 ms 1 ms 2 ms
3 do-gts.tvk.wroc.pl (217.153.188.169) 304 ms 277 ms 322 ms
4 taro-poznan-g0-3-0-42.ipartners.pl (217.153.2.213) 14 ms 12 ms 16 ms
5 taro-wawa-as0-0.ipartners.pl (217.153.3.145) 22 ms 24 ms 16 ms
6 taro2-f0-0-220.ipartners.pl (217.153.3.2) 19 ms 22 ms 17 ms
7 icm-r1-193-219-28-233.rtr.net.icm.edu.pl (193.219.28.233) 87 ms 97 ms 116 ms
8 atman.icm.edu.pl (193.219.28.86) 109 ms 131 ms 103 ms
9 gsr3.oc12.atman.pl (217.17.33.6) 90 ms 82 ms 116 ms
10 dns.atman.pl (217.17.34.10) 155 ms 205 ms 170 ms

Albo szybko naprawili, albo to występuje tylko u ciebie.