Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 31 Jul 2003 14:20:30 +0930
From:      Greg 'groggy' Lehey <grog@lemis.com>
To:        FreeBSD current users <FreeBSD-current@FreeBSD.ORG>, FreeBSD mobile Mailing List <freebsd-mobile@FreeBSD.org>
Subject:   Lucent IBSS mode doesn't work in -CURRENT?
Message-ID:  <20030731045030.GH33447@wantadilla.lemis.com>

next in thread | raw e-mail | index | archive | help

--x7gJcYyRf5ZnuMVj
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
 =20
wi0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> 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
=20
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=3DBSS, 3=3Dad-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=3Don, 0=3Doff):               [ 0 ]
Max sleep time:                         [ 100 ]
WEP encryption:                         [ Off ]
TX encryption key:                      [ 1 ]
Encryption keys:                        [  ][  ][  ][  ]
=20
wi0: <Lucent Technologies WaveLAN/IEEE> 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
=20
wi0: <Lucent Technologies WaveLAN/IEEE> 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
=20
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:
=20
wi0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> 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
=20
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

--x7gJcYyRf5ZnuMVj
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)

iD8DBQE/KKAWIubykFB6QiMRAkEhAJ9tVBw0CABbSVqP0Zad/RZP8FP0pQCfRxPN
ILf/oBfKyLK5FzVvKyMZETs=
=2JL9
-----END PGP SIGNATURE-----

--x7gJcYyRf5ZnuMVj--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030731045030.GH33447>