ALT Linux Community general discussions
 help / color / mirror / Atom feed
From: "Шигапов Ринат" <srk@nevod.ru>
To: ALT Linux Community general discussions <community@lists.altlinux.org>
Subject: Re: [Comm] Wifi - потеря пакетов
Date: Mon, 13 Apr 2009 15:35:18 +0600
Message-ID: <49E30756.90809@nevod.ru> (raw)
In-Reply-To: <49E2FCB5.4090603@nevod.ru>

Шигапов Ринат пишет:
>
>
>
> Карточка rtl8187 довольно популярна, может кому-то удалось добиться 
> устойчивой работы?
>
В качестве временного решения сбавил скорость подключения:
[root@localhost wlan0]# cat /etc/net/ifaces/wlan0/iwconfig
rate 11M

Пакеты при небольшой нагрузке не теряются, но периодически возникает 
большая задержка:
[srk@localhost ~]$ ping 172.16.16.14
PING 172.16.16.14 (172.16.16.14) 56(84) bytes of data.
64 bytes from 172.16.16.14: icmp_seq=1 ttl=255 time=10.0 ms
64 bytes from 172.16.16.14: icmp_seq=2 ttl=255 time=1.96 ms
64 bytes from 172.16.16.14: icmp_seq=3 ttl=255 time=1.95 ms
64 bytes from 172.16.16.14: icmp_seq=4 ttl=255 time=1.86 ms
64 bytes from 172.16.16.14: icmp_seq=5 ttl=255 time=3.90 ms
64 bytes from 172.16.16.14: icmp_seq=6 ttl=255 time=2856 ms
64 bytes from 172.16.16.14: icmp_seq=7 ttl=255 time=1860 ms
64 bytes from 172.16.16.14: icmp_seq=8 ttl=255 time=862 ms
64 bytes from 172.16.16.14: icmp_seq=9 ttl=255 time=1.94 ms
64 bytes from 172.16.16.14: icmp_seq=10 ttl=255 time=1.80 ms
64 bytes from 172.16.16.14: icmp_seq=11 ttl=255 time=1.79 ms
64 bytes from 172.16.16.14: icmp_seq=12 ttl=255 time=1.97 ms
64 bytes from 172.16.16.14: icmp_seq=13 ttl=255 time=2.09 ms
64 bytes from 172.16.16.14: icmp_seq=14 ttl=255 time=2.73 ms
64 bytes from 172.16.16.14: icmp_seq=15 ttl=255 time=28.9 ms
64 bytes from 172.16.16.14: icmp_seq=16 ttl=255 time=693 ms
64 bytes from 172.16.16.14: icmp_seq=17 ttl=255 time=1904 ms
64 bytes from 172.16.16.14: icmp_seq=18 ttl=255 time=902 ms
64 bytes from 172.16.16.14: icmp_seq=19 ttl=255 time=3.57 ms
64 bytes from 172.16.16.14: icmp_seq=20 ttl=255 time=1.80 ms
64 bytes from 172.16.16.14: icmp_seq=21 ttl=255 time=1.83 ms
64 bytes from 172.16.16.14: icmp_seq=22 ttl=255 time=2.87 ms
64 bytes from 172.16.16.14: icmp_seq=23 ttl=255 time=1.84 ms
64 bytes from 172.16.16.14: icmp_seq=24 ttl=255 time=2.56 ms
64 bytes from 172.16.16.14: icmp_seq=25 ttl=255 time=579 ms
64 bytes from 172.16.16.14: icmp_seq=26 ttl=255 time=2963 ms
64 bytes from 172.16.16.14: icmp_seq=27 ttl=255 time=1966 ms
64 bytes from 172.16.16.14: icmp_seq=28 ttl=255 time=967 ms
64 bytes from 172.16.16.14: icmp_seq=29 ttl=255 time=1.83 ms
64 bytes from 172.16.16.14: icmp_seq=30 ttl=255 time=1.96 ms
64 bytes from 172.16.16.14: icmp_seq=31 ttl=255 time=7.56 ms
64 bytes from 172.16.16.14: icmp_seq=32 ttl=255 time=2.17 ms
64 bytes from 172.16.16.14: icmp_seq=33 ttl=255 time=2.05 ms
64 bytes from 172.16.16.14: icmp_seq=34 ttl=255 time=2.09 ms
64 bytes from 172.16.16.14: icmp_seq=35 ttl=255 time=4017 ms
64 bytes from 172.16.16.14: icmp_seq=36 ttl=255 time=3023 ms
64 bytes from 172.16.16.14: icmp_seq=37 ttl=255 time=2025 ms
64 bytes from 172.16.16.14: icmp_seq=38 ttl=255 time=1029 ms
64 bytes from 172.16.16.14: icmp_seq=39 ttl=255 time=36.0 ms
64 bytes from 172.16.16.14: icmp_seq=40 ttl=255 time=1.93 ms
64 bytes from 172.16.16.14: icmp_seq=41 ttl=255 time=1.85 ms
^C
--- 172.16.16.14 ping statistics ---
41 packets transmitted, 41 received, 0% packet loss, time 40139ms
rtt min/avg/max/mdev = 1.795/628.921/4017.823/1052.753 ms, pipe 5

Очень неприятно при работе по ssh.

-- 
С уважением,
        Шигапов Ринат
        инженер-программист ООО "Невод"
        тел. (342)2196960
        JabberID: dxist эт ya.ru 
				



  parent reply	other threads:[~2009-04-13  9:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 10:57 Шигапов Ринат
2009-04-10 11:14 ` Шигапов Ринат
2009-04-13  8:49   ` Шигапов Ринат
2009-04-13  9:00     ` Владимир Гусев
2009-04-13  9:35     ` Шигапов Ринат [this message]
2009-04-14  4:52       ` Бакушкин Михаил

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=49E30756.90809@nevod.ru \
    --to=srk@nevod.ru \
    --cc=community@lists.altlinux.org \
    /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