wi(4) with AirPort only half working

[Frank Wille]

Hi!

Before I try to debug the code on my PowerBook G3 (Pismo) I would like to
know if there is a general, maybe known, problem with wi(4), or if it is a
problem in the macppc if_wi_obio.c frontend.

WLAN with wi(4) seems to work for me, when I configure it with
# ifconfig wi0 inet a.b.c.d ssid myname mkey mykey up

But:

- "ifconfig wi0" does not display the right channel when connected
- "ifconfig wi0 list scan" hangs
- "wlanctl wi0" only displays my own interface

Did anybody else see that on anything other than macppc hardware?

[Frank Wille]

Post by Frank Wille
[...]
- "ifconfig wi0" does not display the right channel when connected
- "ifconfig wi0 list scan" hangs
- "wlanctl wi0" only displays my own interface
Did anybody else see that on anything other than macppc hardware?

Seems I have to rephrase my question:

Is anybody using wi(4) on non-macppc hardware? Then please tell me if
"ifconfig wi0 list scan" works for you and which firmware you are using.

Now I remember that macallan@ told me the behaviour might be firmware
dependant. Does it mean this firmware
wi0: Lucent Firmware: Station (8.70.1)
does not provide the possibility for "list scan" or showing the correct
channel? Then there would be nothing to debug for me.

[Michael van Elst]

Post by Frank Wille
Is anybody using wi(4) on non-macppc hardware? Then please tell me if
"ifconfig wi0 list scan" works for you and which firmware you are using.

On netbsd-5/i386: ifconfig wi0 list scan just waits infinitely and
the interface shows "status: no network". You can interrupt ifconfig,
then down and up the interface to restore operation. dmesg sometimes
shows a "wi0: wi_cmd: busy bit won't clear".

wi0 at pcmcia1 function 0: <Lucent Technologies, WaveLAN/IEEE, Version 01.01, >
wi0: Lucent Firmware: Station (8.10.1)

N.B. wiconfig wi0 -D seems to work and doesn't kill the interface.