wpa_supplicant for ad-hoc mode
dcbw at redhat.com
Thu Mar 5 14:30:47 EST 2009
On Thu, 2009-03-05 at 11:24 -0700, Shawn Rutledge wrote:
> On Thu, Mar 5, 2009 at 4:39 AM, Dan Williams <dcbw at redhat.com> wrote:
> > Yes, all stations in Ad-Hoc mode are essentially independent. Your
> > problem is that the driver is not signaling to the supplicant that it
> > has successfully started the new Ad-Hoc BSS. Because the driver isn't
> > saying "I'm done doing what you requested", the supplicant has no idea
> > that the operation is successful, and times out.
> > If the driver were to send that event, then you wouldn't be having this
> > problem. It doesn't have any relation to what's happening at the other
> > end; it has to do with a buggy driver.
> This code is explicitly de-associating, which I was thinking is not
> the right thing to do in ad-hoc mode:
> wpa_supplicant_disassociate(wpa_s, WLAN_REASON_DEAUTH_LEAVING);
But it's doing this in wpa_supplicant_timeout() function, right? That's
expected, because the timeout triggered when the driver failed to signal
that it had properly joined the adhoc network. The only reason
wpa_supplicant_timeout() gets called is due to the driver bug.
There are many reasons the driver can fail to join/create an adhoc
network. Thus, you cannot expect success from just asking "please
create/join this adhoc network", and the driver *needs* to signal the
success or failure of the operation. Your driver is apparently not
> but you mean if the driver was working properly, that timeout would
> not occur, even if there are no other nodes with the same SSID?
More information about the HostAP