From owner-freebsd-mobile@FreeBSD.ORG Sat Jun 21 04:12:24 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B145937B401 for ; Sat, 21 Jun 2003 04:12:24 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A79643F93 for ; Sat, 21 Jun 2003 04:12:22 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8p1/8.12.8) id h5LBCBPZ088620; Sat, 21 Jun 2003 13:12:11 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200306211112.h5LBCBPZ088620@spider.deepcore.dk> In-Reply-To: <20030619.183809.89278695.imp@bsdimp.com> To: "M. Warner Losh" Date: Sat, 21 Jun 2003 13:12:11 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: mobile@freebsd.org Subject: Re: Getting wi(4) cards talking between -stable & -current ??? X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2003 11:12:25 -0000 It seems M. Warner Losh wrote: > : ifconfig from -stable: > : > : wi0: flags=8843 mtu 1500 > : inet 194.192.25.157 netmask 0xfffffffc broadcast 194.192.25.159 > : ether 00:02:2d:0d:27:8b > : media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps ) > : status: associated > : ssid "FreeBSD IBSS" 1:"" > : stationname "FreeBSD WaveLAN/IEEE node" > : channel 3 authmode OPEN powersavemode OFF powersavesleep 100 > : wepmode OFF weptxkey 1 > : > : ifconfig from -current: > : wi0: flags=8843 mtu 1500 > : inet 194.192.25.158 netmask 0xfffffffc broadcast 194.192.25.159 > : ether 00:02:2d:01:7d:e9 > : media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps ) > : status: associated > : ssid "" > : stationname "FreeBSD WaveLAN/IEEE node" > : channel 3 authmode OPEN powersavemode OFF powersavesleep 100 > : wepmode OFF weptxkey 1 > > What are the firmware versions of these cards? What kinds of adhoc > modes are support differe between firmware versions. The ethernet > addresses suggest that about 700,000 cards were made between the two > which suggests they might not be completely identical. They where bougth together and looks like this: wi0-stable: 802.11 address: 00:02:2d:0d:27:8b wi0-stable: using Lucent Technologies, WaveLAN/IEEE wi0-stable: Lucent Firmware: Station 4.52.01 wi0-current: 802.11 address: 00:02:2d:01:7d:e9 wi0-current: using Lucent Technologies, WaveLAN/IEEE wi0-current: Lucent Firmware: Station (4.52.1) Looks semilar to me ... > I'd try the following: > > 4.8% ifconfig wi0 media autoselect mediaopt ibss-master ssid \ > "SosAtaDriverRocks" channel 3 > > 5.1% ifconfig wi0 media autoselect mediaopt adhoc ssid \ > "SosAtaDriverRocks" channel 3 this fails with the following on -current: ifconfig: SIOCSIFMEDIA (mediaopt): Device not configured So something is not right here, if its a bug or it really should complain here I have no idea... > 4.8% ifconfig wi0 media autoselect mediaopt adhoc ssid \ > "SosAtaDriverRocks" channel 3 > > 5.1% ifconfig wi0 media autoselect mediaopt adhoc,flag0 ssid \ > "SosAtaDriverRocks" channel 3 This gives no errors etc, but the cards cant see each other still... > I don't know the distances between the cards, but you may want to wire > down the speed by applying one of the following: > s=autoselect=DS/2Mbps=g > s=autoselect=DS/1Mbps=g > s=autoselect=DS/5.5Mbps=g > s=autoselect=DS/11Mbps=g > > Finally, there have been many issues with the 5.1 wi driver with > Lucent cards, which it doesn't look like you are hitting, but I > thought I'd warn you. Well, the cards are 2m apart so they should have no problems seeing each other at all... > I'm not sure what else to say. Damn! I thought I was doing something stupid... Anyhow it works with between 4.8-4.8 and 4.8-5.0 but the wi driver has apparently regressed to being useless in 5.1 and -current :( -Søren