Thread: [Madwifi-devel] rate control questions
Status: Beta
Brought to you by:
otaku
From: Baldine, I. <iba...@rt...> - 2005-08-25 16:03:58
|
I noticed that the Atheros chipset provides multiple transmit queues and the madwifi driver takes advantage of that (Is this right?).=20 =20 Question - is the rate control module involved before or after the decision in which queue a packet goes? More to the point - can I design a rate control module that will assign different transmit rates to packets based on the queue they are in? =20 In the same vein (I asked this on madwifi@ list but got no answer): is rate forcing (using iwconfig) a tested feature? I tried it in ad-hoc mode both with older madwifi-bsd and the current madwifi and once I force the rate (in either or both nodes in a 2-node ad-hoc network), they loose communications. 'auto' is the only rate setting that seems to work. Is there something I'm missing? =20 -ilia =20 =20 |
From: Daniel Wu <dy...@gm...> - 2005-08-25 22:19:40
|
On 8/25/05, Baldine, Illia <iba...@rt...> wrote: > In the same vein (I asked this on madwifi@ list but got no answer): is ra= te > forcing (using iwconfig) a tested feature? I tried it in ad-hoc mode both > with older madwifi-bsd and the current madwifi and once I force the rate = (in > either or both nodes in a 2-node ad-hoc network), they loose communicatio= ns. > 'auto' is the only rate setting that seems to work. Is there something I'= m > missing?=20 I have the same problem with the latest CVS code (Aug 25, 2005). Fixing the rate stops the transmissions. This goes for all a/b/g modes and master/ad-hoc/managed. I did a little test where, one acts as a master 802.11g 54Mbps fixed, and one as the client 802.11g 54Mbps auto. The client pings the master. When running tethereal on both, the client captures its own icmp packets on= ly. The master sees the icmp packets from the client and a reply from itself to the client. It seems that the icmp reply packet gets created and gets caught by the hooks in transmission, but doesn't get sent out physically ( I think). In a second scenario, I made the master 54Mbps auto and the client 54Mbps fixed. The client pings the master. The client tethereal captures the icmp request packets, but the master sees nothing on its end. I hope this helps somebody to debug this, --Daniel |
From: Daniel Wu <dy...@gm...> - 2005-08-25 22:28:17
|
> I have the same problem with the latest CVS code (Aug 25, 2005). > Fixing the rate stops the transmissions. This goes for all a/b/g modes > and master/ad-hoc/managed. >=20 >In a second scenario, I made the master 54Mbps auto and the client >54Mbps fixed. I should rephrase that in the master/client modes, 802.11b still works fine when one is fixed and the other is auto rated. But 802.11a/g does not. the Hardware/softare is=20 ath_hal 0.9.14.9 ath_rate_sample: 1.2 ath_pci: 0.9.6.0 (EXPERIMENTAL) ath0: mac5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 kernel 2.6.11-1.27_FC3 02:04.0 Atheros Communications, Inc. AR5212 802.11abg NIC (rev01) miniPCI in a HP/Compaq nc6000 laptop --Daniel |