From: "Chuck Crisler" <ccrisler@vgocom.com>
To: <linux-wireless@vger.kernel.org>
Subject: problem calling the supplicant
Date: Mon, 24 Jan 2011 15:57:55 -0500 [thread overview]
Message-ID: <38B8E33D2F114AFCAF7F0F4C591983BD@ChuckPC> (raw)
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
reply other threads:[~2011-01-24 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38B8E33D2F114AFCAF7F0F4C591983BD@ChuckPC \
--to=ccrisler@vgocom.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox