On Mon, Nov 12, 2007 at 05:59:25PM -0500, Will Dyson wrote:
> That is some pretty nasty latency. You didn't describe the setup for
> your test, so I don't really have any insight into this problem. You
> might want to check the wireless bitrate using the "iwconfig" command.
>
> If the bitrate is really low, then the network latency problem is
> explained. When the bitrate is low, it is much easier for a single
> stream to saturate the connection (making for bad latency).
>
> The output of "iwconfig" and "dmesg | grep rt2x00" would really help
> in debugging this issue.
You are right - its caused by a VERY low bitrate:
flo@heisenberg:~$ sudo iwconfig ra0
ra0 IEEE 802.11g ESSID:"home.rfc822.org"
Mode:Managed Frequency:2.452 GHz Access Point: 00:0C:41:DE:17:FC
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality=47/100 Signal level=-49 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
This is kind of "interesting" as the machine is just next table
as the Access Point - Direct line of sight - about 2m.
The point is that i didnt experience the same problem
back with 2.6.16.16 and the out-of-tree ralink driver.
Here is the driver i didnt experience the problem with:
flo@heisenberg:~$ sudo modinfo /lib/modules/2.6.16.16-heisenberg/extra/rt2500.ko
filename: /lib/modules/2.6.16.16-heisenberg/extra/rt2500.ko
license: GPL
description: Ralink RT2500 802.11g WLAN driver 1.1.0 BETA3 2005/07/31
author: http://rt2x00.serialmonkey.com
alias: pci:v00001814d00000201sv*sd*bc*sc*i*
depends:
vermagic: 2.6.16.16-heisenberg preempt PENTIUM4 gcc-4.0
parm: debug:Enable level: accepted values: 1 to switch debug on, 0 to switch debug off. (i)
parm: ifname:Network device name (default ra%d) (s)
With 2.6.24-rc2 current git the rt2x00 driver is compiled fixed into
the kernel - No rt2x00 messages but here is what i found:
flo@heisenberg:~$ dmesg | egrep "rt2x00|ra0|phy0"
phy0: Selected rate control algorithm 'simple'
ADDRCONF(NETDEV_UP): ra0: link is not ready
ra0: Initial auth_alg=0
ra0: authenticate with AP 00:0c:41:de:17:fc
ra0: RX authentication from 00:0c:41:de:17:fc (alg=0 transaction=2 status=0)
ra0: authenticated
ra0: associate with AP 00:0c:41:de:17:fc
ra0: RX AssocResp from 00:0c:41:de:17:fc (capab=0x401 status=0 aid=1)
ra0: associated
ra0: switched to short barker preamble (BSSID=00:0c:41:de:17:fc)
ADDRCONF(NETDEV_CHANGE): ra0: link becomes ready
ra0: Initial auth_alg=0
ra0: authenticate with AP 00:0c:41:de:17:fc
ra0: RX authentication from 00:0c:41:de:17:fc (alg=0 transaction=2 status=0)
ra0: authenticated
ra0: associate with AP 00:0c:41:de:17:fc
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: authentication frame received from 00:0c:41:de:17:fc, but not in authenticate state - ignored
ra0: RX ReassocResp from 00:0c:41:de:17:fc (capab=0x401 status=0 aid=1)
ra0: associated
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: association frame received from 00:0c:41:de:17:fc, but not in associate state - ignored
ra0: no IPv6 routers present
Another interesting point is that at the back of the PCI Card the
"TxLink" led is permanently lit - I dont think this was the case
with the older driver - at least i cant remember it beeing lit.
Flo
--
Florian Lohoff flo@xxxxxxxxxx +49-171-2280134
Those who would give up a little freedom to get a little
security shall soon have neither - Benjamin Franklin
Attachment:
signature.asc
Description: Digital signature
