From owner-freebsd-current@FreeBSD.ORG Mon May 17 09:20:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88C9416A516; Mon, 17 May 2004 09:20:28 -0700 (PDT) Received: from smtp.tznet.com (smtp.tznet.com [66.170.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7A2943D1D; Mon, 17 May 2004 09:20:27 -0700 (PDT) (envelope-from scottp@tznet.com) Received: from mail.tznet.com (mail.tznet.com [66.170.64.2]) by smtp.tznet.com (8.12.11/8.12.10) with ESMTP id i4HGK3lt027259; Mon, 17 May 2004 11:20:07 -0500 (CDT) Date: Mon, 17 May 2004 11:20:02 -0500 (CDT) From: Scott Pilz To: Sam Leffler In-Reply-To: <200405170842.52770.sam@errno.com> Message-ID: <20040517111612.Q45026@mail.tznet.com> References: <20040516210816.M45998@acelere.net> <40A85B24.1000300@mikulas.com> <20040517063129.J10292@mail.tznet.com> <200405170842.52770.sam@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-T-Net-Virus-Scan: 66.170.64.6: Clean X-Mailman-Approved-At: Tue, 18 May 2004 04:50:44 -0700 cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: hostap TX fix in 5.x [Fwd: Re: wi hostap speed] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 May 2004 16:20:28 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I'm certainly not looking for anything pretty. Should it not be possible to determine what the TX rate would be for the associated station and simply set frmhdr.wi_tx_rate to 110 if the TX rate is 11mbit, otherwise lay off and don't touch it? This wouldn't be a "perfect fix" by any-means but again, I'm not looking for anything pretty, just something to get associated stations up to 11mbit when they can support it. It is my understanding that frmhdr.wi_tx_rate, though specified, is not changed in the driver, thus defaults to 0 which would be 2mbit TX (and that is exactly what we are seeing). Scott On Mon, 17 May 2004, Sam Leffler wrote: > On Monday 17 May 2004 04:38 am, Scott Pilz wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Who normally works on the wi driver? "frmhdr.wi_tx_rate = 110" > > works great (thanks James) but I am unable to find the syntax/variable > > where the current TX-RATE is stored. A simple if tx-rate=11 { > > frmhdr.wi_tx_rate = 110; } would keep auto-fallback working. Currently the > > system works great (I seen as far as 600KB/sec last night during testing) > > but when the signal drops and the driver tries for 5.5 or 2, packets are > > lost. I recall in earlier releases of 5.x there was a 'DataRate' display > > on 'wicontrol -l', however in CURRENT this seems to be missing. > > In the past Warner and I have worked on the driver but neither has time and > noone else has stepped up. It sounds like you've locked the xmit rate to a > fixed value instead of allowing the firmware to select the "best rate." This > sounds as though something else is set wrong to make the best rate operation > not work right. > > FWIW netbsd uses an adaptive rate control algorithm to select the xmit rate. > Reports are that this algorithm does a better job than the firmware algorithm > for choosing xmit rate when operating in hostap mode. > > Sam > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAqOYz2REUg6gjWxgRAr4lAKCVpkz8DbbvjlVOaeBP6C1IzrfEJQCgzXxy 0k1CJjGzc0wiJI84LKNvNE0= =OnZl -----END PGP SIGNATURE-----