From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Kalle Valo <kvalo@adurom.com>
Cc: <j@w1.fi>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] wpa_supplicant: Set configured auth_algs
Date: Mon, 14 Nov 2011 10:57:39 +0530 [thread overview]
Message-ID: <20111114052738.GA9563@vasanth-laptop> (raw)
In-Reply-To: <877h35af6x.fsf@purkki.adurom.net>
On Sat, Nov 12, 2011 at 11:00:06AM +0200, Kalle Valo wrote:
> Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com> writes:
>
> > In Ap mode, Authentication algorithm is reset in
> > hostapd_config_defaults_bss() and never be set to the configured
> > one. This would pass the default auth_algs (OPEN|SHARED) to driver
> > and cause authentication isseues.
>
> Shouldn't you send this to the hostap mailing list?
Oops, forgot it, as the ath6kl patch has a reference to this patch I added
linux-wireless list but missed to add the one meant for hostap. Thanks for
pointing this out.
Vasanth
prev parent reply other threads:[~2011-11-14 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 15:02 [PATCH] wpa_supplicant: Set configured auth_algs Vasanthakumar Thiagarajan
2011-11-12 9:00 ` Kalle Valo
2011-11-14 5:27 ` Vasanthakumar Thiagarajan [this message]
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=20111114052738.GA9563@vasanth-laptop \
--to=vthiagar@qca.qualcomm.com \
--cc=j@w1.fi \
--cc=kvalo@adurom.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