From: Christian Lamparter <chunkeey@googlemail.com>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com
Subject: [PATCH v3] p54: connect to 11w protected networks
Date: Tue, 4 Sep 2012 15:19:33 +0200 [thread overview]
Message-ID: <E1TA0re-00059m-CD@debian64.localnet> (raw)
Previously, it was not possible to connect
to networks which requires 11w to be supported
by the stations.
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) |
--
1.7.10.4
next reply other threads:[~2012-09-07 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 13:19 Christian Lamparter [this message]
2012-09-07 16:51 ` [PATCH v3] p54: connect to 11w protected networks Dan Williams
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=E1TA0re-00059m-CD@debian64.localnet \
--to=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).