On Monday 24 May 2010 23:16:48 David H. Lynch Jr. wrote: > I am trying to kick carl9170 1.0.9 into either add-hoc or monitor > mode or anything else where I can xmit to any wireless device. I do not > care if the receiving device is interested - so long as the radio ACK's > the packet, which it should do automatically. iwconfig and all other wext-based wireless-tools are obsolete. The new CLI "iw" can be found on: http://wireless.kernel.org/en/users/Documentation/iw > I tried iwconfig wl_ath mode ad-hoc > And I get and errror: > > root# iwconfig wl_ath mode ad-hoc > Error for wireless request "Set Mode" (8B06) : > SET failed on device wl_ath ; Device or resource busy. This is expected. The wl_ath interface must be *down* before you can chance the operation mode of the master interface. try: (of course, after calling: ifconfig wl_ath down) iw dev wlanX ibss join <SSID> freq/channel <MHz/Chan No.> > root# iwconfig wl_ath mode monitor > Error for wireless request "Set Mode" (8B06) : > SET failed on device wl_ath ; Device or resource busy. iw dev wlanX set monitor [otherbss control ...] > root# iwconfig wl_ath mode master > Error for wireless request "Set Mode" (8B06) : > SET failed on device wl_ath ; Invalid argument. Master/Accesspoint mode is no longer fully implemented into the kernel and therefore needs a userspace daemon: hostapd. http://wireless.kernel.org/en/users/Documentation/hostapd > I can add something to the driver if needed if you could recommend > another wireless driver for a reference. Well, we could add a beacon scheduler. This way we might be able to support more than just one AP/IBSS interface. But this is really complicated as the whole CAB implementation needs to be extended to support multiple (concurrent) AP/IBSS links. (And of course, there's the problem of the shared TSF in such a configuration, so this might not be feasible after all...) Regards, Chr -- 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
