From owner-freebsd-current@FreeBSD.ORG Thu Jul 31 00:31:22 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 7F4CC37B405 for ; Thu, 31 Jul 2003 00:31:22 -0700 (PDT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 7860543FAF for ; Thu, 31 Jul 2003 00:31:21 -0700 (PDT) (envelope-from ltning@anduin.net) Received: (qmail 87052 invoked from network); 31 Jul 2003 07:31:18 -0000 Received: from celduin.net (HELO anduin.net) (81.0.162.106) by anduin.net with SMTP; 31 Jul 2003 07:31:18 -0000 Date: Thu, 31 Jul 2003 09:30:31 +0200 From: Eirik Oeverby To: Greg 'groggy' Lehey Message-Id: <20030731093031.17deae97.ltning@anduin.net> In-Reply-To: <20030731045030.GH33447@wantadilla.lemis.com> References: <20030731045030.GH33447@wantadilla.lemis.com> X-Mailer: Sylpheed version 0.9.2 (GTK+ 1.2.10; i386-portbld-freebsd5.1) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=.8PBFHQ8OXe7i4)" cc: freebsd-current@freebsd.org Subject: Re: Lucent IBSS mode doesn't work in -CURRENT? 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: Thu, 31 Jul 2003 07:31:22 -0000 --=.8PBFHQ8OXe7i4) Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hey, I have a few Orinoco cards, and they 'work' in both ad-hoc and infrastructure mode. However with dhclient it gets tricky, because it will only work the first time dhclient assigns an address to the card. Whenever it tries to refresh it or whatever, I start getting those timeout and busy bit errors, and network connectivity drops. This usually happens within a few minutes or latest after 30 minutes or so - probably depending on your dhcpd/dhclient configuration. Configuring a static IP lets me use the card, and it seems stable. I am really glad someone else is seeing this, perhaps it can get fixed some day :) Oh and btw.. Get the *latest* firmware onto all your cards. That is essential for anything to work right at all.. /Eirik On Thu, 31 Jul 2003 14:20:30 +0930 Greg 'groggy' Lehey wrote: > Earlier this month I sent a message saying that my wireless card > (Orinoco) doesn't work at all any more. In the meantime, I've > narrowed the problem down to IBSS ("ad-hoc") mode: it works fine in > BSS (base station) mode. I'd like to know if *anybody* is using IBSS > (maybe with Orinoco cards) on a -CURRENT newer than about mid-May. > > Here's a summary of what I see: > > It happens on two different cards with different firmware. The > ifconfig and wicontrol outputs look identical modulo MAC address and > IBSS channel. > > wi0: flags=8802 mtu 1500 > ether 00:02:2d:04:09:3a > media: IEEE 802.11 Wireless Ethernet autoselect (none) > ssid "" > stationname "FreeBSD WaveLAN/IEEE node" > channel -1 authmode OPEN powersavemode OFF powersavesleep 100 > wepmode OFF weptxkey 1 > > NIC serial number: [ ] > Station name: [ FreeBSD WaveL ] > SSID for IBSS creation: [ ] > Current netname (SSID): [ ] > Desired netname (SSID): [ ] > Current BSSID: [ 00:00:00:00:00:00 ] > Channel list: [ 7ff ] > IBSS channel: [ 3 ] > Current channel: [ 65535 ] > Comms quality/signal/noise: [ 0 0 0 ] > Promiscuous mode: [ Off ] > Process 802.11b Frame: [ Off ] > Intersil-Prism2 based card: [ 0 ] > Port type (1=BSS, 3=ad-hoc): [ 1 ] > MAC address: [ 00:02:2d:04:09:3a ] > TX rate (selection): [ 0 ] > TX rate (actual speed): [ 0 ] > RTS/CTS handshake threshold: [ 2312 ] > Create IBSS: [ Off ] > Access point density: [ 1 ] > Power Mgmt (1=on, 0=off): [ 0 ] > Max sleep time: [ 100 ] > WEP encryption: [ Off ] > TX encryption key: [ 1 ] > Encryption keys: [ ][ ][ ][ ] > > wi0: at port 0x100-0x13f irq 11 > function 0 config 1 on pccard1 wi0: 802.11 address: 00:02:2d:04:09:3a > wi0: using Lucent Technologies, WaveLAN/IEEE > wi0: Lucent Firmware: Station (6.6.1) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > wi0: at port 0x100-0x13f irq 11 > function 0 config 1 on pccard1 wi0: 802.11 address: 00:02:2d:1e:d9:60 > wi0: using Lucent Technologies, WaveLAN/IEEE > wi0: Lucent Firmware: Station (6.16.1) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > When I run dhclient against the first card, I don't get a connection, > and the other end doesn't see any data traffic, but it finds the > network: > > wi0: flags=8843 mtu 1500 > inet6 fe80::202:2dff:fe04:93a%wi0 prefixlen 64 scopeid 0x4 > inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255 > ether 00:02:2d:04:09:3a > media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps) > status: associated > ssid FOOXX 1:FOOXX > stationname "FreeBSD WaveLAN/IEEE node" > channel 3 authmode OPEN powersavemode OFF powersavesleep 100 > wepmode OFF weptxkey 1 > > I had guessed that it might be turning WEP on without saying so, but > setting WEP on at both ends didn't help either. > > The second card is much worse than the first: when I try to start > dhclient against it, I get the following messages: > > wi0: timeout in wi_cmd 0x0002; event status 0x8080 > wi0: timeout in wi_cmd 0x0121; event status 0x8080 > wi0: wi_cmd: busy bit won't clear. > > This last one continues forever. At least the keyboard is locked, so > I can't do anything (not even get into ddb, which might have been > useful). While trying to power down I got these messages: > > wi0: failed to allocate 2372 bytes on NIC. > wi0: tx buffer allocateion failed (error 12) > > After that, it continued until I finally managed to power down. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers > --=.8PBFHQ8OXe7i4) Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/KMWadAvR8ct7fEcRAoESAJ9IDMItuF7RQIZy5P2FITTcx0ebsQCfcwB6 fEkny1dg1JCfuFx24r9c0SE= =6v0Y -----END PGP SIGNATURE----- --=.8PBFHQ8OXe7i4)--