Dan Williams wrote:
On Thu, 2008-08-07 at 19:43 +0100, Dave wrote:
That said, what's wrong with the ap_scan=2 mode? You've stated it's
not great (and I'm prepared to believe it), but what is the actual problem?
<snip explanation>
Thanks for that.
I had a reread of <http://hostap.epitest.fi/wpa_supplicant/devel/driver_wrapper.html>.
As a FullMAC driver without support for selecting the BSSID to associate
with (or frequency in Managed mode), the only way I can see to make the
driver work with ap_scan=1 is to silently ignore the SIOCSIWFREQ and
SIOCSIWAP. I don't think this is an approach I would want to pursue.
Well, the current orinoco driver returns "success" (0) for SIOCSIWAP on
Agere firmware.
borken dkilroy # dmesg | grep eth1
eth1: Hardware identity 0001:0001:0004:0002
eth1: Station identity 001f:0001:0008:0048
eth1: Firmware determined as Lucent/Agere 8.72
eth1: Attempting to download firmware agere_sta_fw.bin
<snip fw download>
eth1: Hardware identity 0001:0001:0004:0002
eth1: Station identity 001f:0002:0009:0030
eth1: Firmware determined as Lucent/Agere 9.48
<snip capabilities>
eth1: ready
eth1: orinoco_cs at 0.0, irq 11, io 0x0100-0x013f
eth1: New link status: Connected (0001)
borken dkilroy # iwlist eth1 scan essid MONTY
eth1 Scan completed :
Cell 01 - Address: 00:18:4D:06:45:76
ESSID:"MONTY"
Mode:Master
Channel:5
<snip detail>
borken dkilroy # iwconfig eth1 ap 00:18:4d:06:45:76
Error for wireless request "Set AP Address" (8B14) :
SET failed on device eth1 ; Operation not supported.
borken dkilroy # iwconfig eth1 ap off
borken dkilroy #
The above is running with my patchset, but I haven't touched the SIOCSIWAP handler. Honest.
I'll have a think.
Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
