> On Sunday 17 August 2008, Lars Ericsson wrote: > > > > > > > > Have tried using the wpa_supplicant and got the -EBUSY from > > > > ieee80211_ioctl_siwmode(). > > > > > > As usual: The interface must be down when changing working mode. > > > OK, I found the problem. When the wpa_supplicant start it open the interface with mode=0. wpa_driver_wext_set_mode() makes iwr.u.mode = mode ? IW_MODE_ADHOC : IW_MODE_INFRA When the mode, at a later time, is actually set with wpa_cli, the device is open and will reject the setting. This must be a BUG in the wpa_supplicant. > > > > Two tests cases, but same behaviour: > > > > 1) Linx.git: 2.6.26 and wpa_supplicant 0.5.9 > > > > 2) rt2x00.git: Version 2.2.0 and wpa_supplicant 0.5.9 > > > > > > Are any beacons going out? Is there anything in the logs which > > > indicates what is happening? > > > > > > > As you can se in the trace below, the configuration > proceeds and the adhoc > > is created. > > The warnon might give some clues. > > So how about those beacons? are they getting out? > After patching the wpa_suplicant (0.5.9) adhoc works. When first started, as the only part in the adhoc net, the driver just scans around for other adhoc members. This happen in mac80211 state 4 and no beacons are sent, as far as I can tell. Only probe requests are sent. When an other node (N2) shows up in the same adhoc net work, N2 starts sending beacons immediately. The RT61 catch that and merge that ibss, switch to state 5 and all is fine. At this time ping works in both directions. When removing the second note, leaving the RT61 alone, RT61 starts sending beacons, still in state 5. /Lars -- 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
