* problem calling the supplicant
@ 2011-01-24 20:57 Chuck Crisler
0 siblings, 0 replies; only message in thread
From: Chuck Crisler @ 2011-01-24 20:57 UTC (permalink / raw)
To: linux-wireless
I have found a problem that is causing my communication with the supplicant
to get confused. I call the supplicant via wpa_ctrl_request(). Sometimes the
commands actually timeout. When that happens, the call to select() returns 0
which causes the wpa_ctrl_request to return -2. From then onward, the
response to all commands is the actual response to the previous command.
That causes my state machine to fail. What should I be doing when this
timeout situation occurs? It looks like I could simply make a subsequent
call into the ctrl_request with a NULL command (with length == 0) to get it
to execute the select() again, though I may want to modify
wpa_ctrl_request() to skip the send() if there is a NULL command. I know
that my missing response will ultimately be returned. Has anyone else seen
anything like this?
Thank you,
Chuck Crisler
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-01-24 20:58 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-24 20:57 problem calling the supplicant Chuck Crisler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox