From owner-freebsd-current@FreeBSD.ORG Mon Dec 8 11:27:39 2003 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 1981916A4CE; Mon, 8 Dec 2003 11:27:39 -0800 (PST) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E08443D1D; Mon, 8 Dec 2003 11:27:37 -0800 (PST) (envelope-from sam@errno.com) Received: from 66.127.85.91 ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.9) with ESMTP id hB8JRZHQ037938 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 8 Dec 2003 11:27:36 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: Soren Schmidt Date: Mon, 8 Dec 2003 11:30:39 -0800 User-Agent: KMail/1.5.3 References: <200312081900.hB8J0mxU071141@spider.deepcore.dk> In-Reply-To: <200312081900.hB8J0mxU071141@spider.deepcore.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312081130.39451.sam@errno.com> cc: Erwin Lansing cc: current@FreeBSD.ORG Subject: Re: Status of wi(4) 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, 08 Dec 2003 19:27:39 -0000 On Monday 08 December 2003 11:00 am, Soren Schmidt wrote: > It seems Sam Leffler wrote: > > > > My MA401 w/ later station firmware (1.3.4) works fine. The previous > > > > wi problems were with Lucent cards and appear to have been resolved. > > > > > > No! lucents even with the newest firmware 8.x.x still doesn't work in > > > either adhoc mode. I can get it to contact an AP but thats all.. > > > > My last testing of wi for Prism and Lucent both worked with adhoc mode. > > I am aware of your issues with adhoc mode for atwi cards. I will test > > again but, as usual, details are more useful than "it don't work". > > Well, I put two of these: > > wi0: at port 0x100-0x13f irq 11 function > 0 co nfig 1 on pccard0 > wi0: 802.11 address: xx:xx:xx:xx:xx:xx > wi0: using Lucent Technologies, WaveLAN/IEEE > wi0: Lucent Firmware: Station (8.10.1) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > in laptops running 5.2-soontobe, and they can't find each other nor talk > adhoc to the other even if one is running win2K. Running both in win2k > works and so does talking to an AP. > The problems with atwi that you are referring to are very semilar so to > me it suggests our 80211 code which is common has something todo with the > problems at hand. And I just setup two laptops; one with a Senao (Prism 2, STA firmware 1.4.9) card and the other with a Lucent card (STA firmware 6.6.1). Each was configured in adhoc mode and a fixed IP address. They found each other fine and ping and netperf work perfectly. No WEP though I doubt that would matter. One laptop is running current from today. The other is running an older system from when I last chased these complaints (I'm updating to verify it's not got a local fix). I know you've had ongoing adhoc mode problems and I'm aware of issues for devices that depend on the 802.11 layer to handle management frames, but I've always been under the impression the wi driver worked ok since my last fix (rev 1.7 if net80211/ieee80211_output.c). Sam