From: Aleksandr Fetininsky <sashurik@telecont.ru>
To: Community <community@altlinux.ru>
Subject: [Comm] Время прохождения ping'а
Date: Wed, 21 May 2003 17:22:54 +0400
Message-ID: <20030521172254.0b7b9fd6.sashurik@telecont.ru> (raw)
Здравствуйте.
В последнее время появились проблемы с Интернетом. При получениии
любых данных (почта, web, etc.) возникают постоянные паузы, когда
не поступает ничего (смотрю по gkrellm). Пингую шлюз провайдера,
вижу следующее:
PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data.
64 bytes from 192.168.0.4: icmp_seq=1 ttl=255 time=21994 ms
64 bytes from 192.168.0.4: icmp_seq=2 ttl=255 time=20988 ms
64 bytes from 192.168.0.4: icmp_seq=3 ttl=255 time=20023 ms
64 bytes from 192.168.0.4: icmp_seq=4 ttl=255 time=19038 ms
64 bytes from 192.168.0.4: icmp_seq=5 ttl=255 time=18087 ms
64 bytes from 192.168.0.4: icmp_seq=6 ttl=255 time=17094 ms
64 bytes from 192.168.0.4: icmp_seq=7 ttl=255 time=16101 ms
64 bytes from 192.168.0.4: icmp_seq=8 ttl=255 time=16085 ms
64 bytes from 192.168.0.4: icmp_seq=9 ttl=255 time=15132 ms
64 bytes from 192.168.0.4: icmp_seq=10 ttl=255 time=14139 ms
64 bytes from 192.168.0.4: icmp_seq=11 ttl=255 time=13324 ms
64 bytes from 192.168.0.4: icmp_seq=12 ttl=255 time=12331 ms
64 bytes from 192.168.0.4: icmp_seq=13 ttl=255 time=11351 ms
64 bytes from 192.168.0.4: icmp_seq=14 ttl=255 time=10358 ms
64 bytes from 192.168.0.4: icmp_seq=15 ttl=255 time=9378 ms
64 bytes from 192.168.0.4: icmp_seq=16 ttl=255 time=8386 ms
64 bytes from 192.168.0.4: icmp_seq=17 ttl=255 time=7405 ms
64 bytes from 192.168.0.4: icmp_seq=18 ttl=255 time=6412 ms
64 bytes from 192.168.0.4: icmp_seq=19 ttl=255 time=5431 ms
64 bytes from 192.168.0.4: icmp_seq=20 ttl=255 time=4439 ms
64 bytes from 192.168.0.4: icmp_seq=21 ttl=255 time=3458 ms
64 bytes from 192.168.0.4: icmp_seq=22 ttl=255 time=2465 ms
64 bytes from 192.168.0.4: icmp_seq=23 ttl=255 time=1473 ms
64 bytes from 192.168.0.4: icmp_seq=24 ttl=255 time=653 ms
64 bytes from 192.168.0.4: icmp_seq=25 ttl=255 time=414 ms
64 bytes from 192.168.0.4: icmp_seq=26 ttl=255 time=712 ms
64 bytes from 192.168.0.4: icmp_seq=27 ttl=255 time=178 ms
64 bytes from 192.168.0.4: icmp_seq=28 ttl=255 time=175 ms
64 bytes from 192.168.0.4: icmp_seq=29 ttl=255 time=319 ms
64 bytes from 192.168.0.4: icmp_seq=30 ttl=255 time=658 ms
64 bytes from 192.168.0.4: icmp_seq=31 ttl=255 time=17805 ms
64 bytes from 192.168.0.4: icmp_seq=32 ttl=255 time=16829 ms
64 bytes from 192.168.0.4: icmp_seq=33 ttl=255 time=15893 ms
64 bytes from 192.168.0.4: icmp_seq=34 ttl=255 time=14914 ms
64 bytes from 192.168.0.4: icmp_seq=35 ttl=255 time=13920 ms
64 bytes from 192.168.0.4: icmp_seq=36 ttl=255 time=12939 ms
64 bytes from 192.168.0.4: icmp_seq=37 ttl=255 time=11956 ms
64 bytes from 192.168.0.4: icmp_seq=38 ttl=255 time=10962 ms
64 bytes from 192.168.0.4: icmp_seq=39 ttl=255 time=9982 ms
64 bytes from 192.168.0.4: icmp_seq=40 ttl=255 time=8998 ms
64 bytes from 192.168.0.4: icmp_seq=41 ttl=255 time=8004 ms
64 bytes from 192.168.0.4: icmp_seq=42 ttl=255 time=7021 ms
64 bytes from 192.168.0.4: icmp_seq=43 ttl=255 time=6026 ms
64 bytes from 192.168.0.4: icmp_seq=44 ttl=255 time=5047 ms
64 bytes from 192.168.0.4: icmp_seq=45 ttl=255 time=4052 ms
64 bytes from 192.168.0.4: icmp_seq=46 ttl=255 time=3069 ms
64 bytes from 192.168.0.4: icmp_seq=47 ttl=255 time=2074 ms
64 bytes from 192.168.0.4: icmp_seq=48 ttl=255 time=1135 ms
64 bytes from 192.168.0.4: icmp_seq=49 ttl=255 time=1058 ms
64 bytes from 192.168.0.4: icmp_seq=50 ttl=255 time=141 ms
64 bytes from 192.168.0.4: icmp_seq=51 ttl=255 time=2248 ms
64 bytes from 192.168.0.4: icmp_seq=52 ttl=255 time=1256 ms
64 bytes from 192.168.0.4: icmp_seq=53 ttl=255 time=483 ms
64 bytes from 192.168.0.4: icmp_seq=54 ttl=255 time=485 ms
64 bytes from 192.168.0.4: icmp_seq=55 ttl=255 time=629 ms
64 bytes from 192.168.0.4: icmp_seq=56 ttl=255 time=154 ms
64 bytes from 192.168.0.4: icmp_seq=57 ttl=255 time=13229 ms
64 bytes from 192.168.0.4: icmp_seq=58 ttl=255 time=12266 ms
64 bytes from 192.168.0.4: icmp_seq=59 ttl=255 time=11271 ms
64 bytes from 192.168.0.4: icmp_seq=60 ttl=255 time=10292 ms
64 bytes from 192.168.0.4: icmp_seq=61 ttl=255 time=9313 ms
64 bytes from 192.168.0.4: icmp_seq=62 ttl=255 time=8318 ms
64 bytes from 192.168.0.4: icmp_seq=63 ttl=255 time=7335 ms
64 bytes from 192.168.0.4: icmp_seq=64 ttl=255 time=6354 ms
64 bytes from 192.168.0.4: icmp_seq=65 ttl=255 time=5358 ms
64 bytes from 192.168.0.4: icmp_seq=66 ttl=255 time=4377 ms
64 bytes from 192.168.0.4: icmp_seq=67 ttl=255 time=3397 ms
64 bytes from 192.168.0.4: icmp_seq=68 ttl=255 time=2401 ms
64 bytes from 192.168.0.4: icmp_seq=69 ttl=255 time=1421 ms
64 bytes from 192.168.0.4: icmp_seq=70 ttl=255 time=924 ms
64 bytes from 192.168.0.4: icmp_seq=71 ttl=255 time=158 ms
--- 192.168.0.4 ping statistics ---
75 packets transmitted, 71 received, 5% packet loss, time 74183ms
rtt min/avg/max/mdev = 141.492/7768.022/21994.602/6316.800 ms,
pipe 22
Бывает, что макс. время ответа доходит до 50 секунд.
Есть ли к.л. общепринятые стандарты (критерии) на макс. время
ответа, при постоянном превышении которого можно предъявлять
претензии в support провайдера на качество оказываемых услуг?
И что означает pipe 22?
--
Александр
next reply other threads:[~2003-05-21 13:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 13:22 Aleksandr Fetininsky [this message]
2003-05-21 21:34 ` Roman S
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030521172254.0b7b9fd6.sashurik@telecont.ru \
--to=sashurik@telecont.ru \
--cc=community@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Community general discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community/0 community/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community community/ http://lore.altlinux.org/community \
mandrake-russian@linuxteam.iplabs.ru community@lists.altlinux.org community@lists.altlinux.ru community@lists.altlinux.com
public-inbox-index community
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git