From: Dan Williams <dcbw@redhat.com>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH v3] p54: connect to 11w protected networks
Date: Fri, 07 Sep 2012 11:51:04 -0500 [thread overview]
Message-ID: <1347036664.8913.1.camel@dcbw.foobar.com> (raw)
In-Reply-To: <E1TA0re-00059m-CD@debian64.localnet>
On Tue, 2012-09-04 at 15:19 +0200, Christian Lamparter wrote:
> Previously, it was not possible to connect
> to networks which requires 11w to be supported
> by the stations.
If at all possible if we can do this without module parameters, that
would be great. Otherwise how is userspace supposed to connect to a
W-capable network without twiddling driver-specific module options,
something we've tried really hard to not do? Module options really
aren't any different than private ioctls or IWPRIV commands...
Dan
> Note:
>
> As all current (and old) firmwares corrupt
> incoming, protected management frames, the
> decryption offloading needs to be disabled.
>
> This can be done by loading the p54common
> module with the nohwcrypt=1 parameter.
>
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> v2->v3:
> - fixed modparam_nohwcrypt typo
> (Yes, v2 never compiled :( )
>
> Regards,
> Christian
> ---
> drivers/net/wireless/p54/main.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/net/wireless/p54/main.c b/drivers/net/wireless/p54/main.c
> index 5e91ad0..8ab5aef 100644
> --- a/drivers/net/wireless/p54/main.c
> +++ b/drivers/net/wireless/p54/main.c
> @@ -739,6 +739,17 @@ struct ieee80211_hw *p54_init_common(size_t priv_data_len)
> IEEE80211_HW_PS_NULLFUNC_STACK |
> IEEE80211_HW_REPORTS_TX_ACK_STATUS;
>
> + if (modparam_nohwcrypt) {
> + /*
> + * Only support MFP, if the hardware crypto engine
> + * is disabled, as the firmware's rx-path corrupts
> + * incoming CCMP encrypted RX mgmt frames.
> + * However, if no rx key is uploaded, the firmware
> + * passes the unencrypted frame to the driver.
> + */
> + dev->flags |= IEEE80211_HW_MFP_CAPABLE;
> + }
> +
> dev->wiphy->interface_modes = BIT(NL80211_IFTYPE_STATION) |
> BIT(NL80211_IFTYPE_ADHOC) |
> BIT(NL80211_IFTYPE_AP) |
next prev parent reply other threads:[~2012-09-07 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 13:19 [PATCH v3] p54: connect to 11w protected networks Christian Lamparter
2012-09-07 16:51 ` Dan Williams [this message]
2012-09-07 17:05 ` Christian Lamparter
2012-09-10 12:28 ` Kalle Valo
2012-09-10 15:59 ` Christian Lamparter
2012-09-10 16:49 ` Dan Williams
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=1347036664.8913.1.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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;
as well as URLs for NNTP newsgroup(s).