From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Ivo Van Doorn <ivdoorn@gmail.com>
Cc: "users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [rt2x00-users] [PATCH][RFC/RFT] rt2800: Implement selectable support for 802.11w (MFP)
Date: Thu, 10 May 2012 16:21:00 +0200 [thread overview]
Message-ID: <4FABCECC.30709@01019freenet.de> (raw)
In-Reply-To: <CAOZOX0Vax7HTsND=vi+c6vamtvWaWW9omWu1CM-=vWsrAf4fgQ@mail.gmail.com>
Hi Ivo,
Ivo Van Doorn wrote:
> Hi,
>
> On Thu, May 10, 2012 at 12:55 PM, Andreas Hartmann
> <andihartmann@01019freenet.de> wrote:
>> Hello!
>>
>> Ivo Van Doorn schrieb:
>>> Hi,
>>>
>>> On Thu, May 10, 2012 at 9:19 AM, Andreas Hartmann
>>> <andihartmann@01019freenet.de> wrote:
>>>> This patch adds support for 802.11w for rt2800. This is achieved by
>>>> using the 802.11w implementation in mac80211.
>>>>
>>>> To get this working, it is necessary to disable hw encryption of
>>>> rt2800pci / rt2800usb, because I don't know of any support in hardware
>>>> for 802.11w and therefore let mac80211 do the whole job.
>>>>
>>>> The user can enable 802.11w with the new mod parameter enablemfp.
>>>> Enabling MFP disables hw encryption.
>>>>
>>>> 802.11w is deactivated per default.
>>>>
>>>> Tested with rt2860 and rt3572.
>>>>
>>>> This is a workaround as long as there isn't hardware support implemented
>>>> in the driver.
>>>>
>>>> Signed-off-by: Andreas Hartmann <andihartmann@01019freenet.de>
>>>> ---
>>>> diff -ur compat-wireless-2012-04-26.orig/drivers/net/wireless/rt2x00/rt2800lib.c compat-wireless-2012-04-26/drivers/net/wireless/rt2x00/rt2800lib.c
>>>> --- compat-wireless-2012-04-26.orig/drivers/net/wireless/rt2x00/rt2800lib.c 2012-04-26 22:10:30.000000000 +0200
>>>> +++ compat-wireless-2012-04-26/drivers/net/wireless/rt2x00/rt2800lib.c 2012-05-09 11:37:48.463278177 +0200
>>>> @@ -4519,6 +4519,15 @@
>>>> IEEE80211_HW_AMPDU_AGGREGATION |
>>>> IEEE80211_HW_REPORTS_TX_ACK_STATUS;
>>>>
>>>> + /*
>>>> + * Enable support for 802.11w in mac80211. hwencryption must be disabled
>>>> + */
>>>> + if (!test_bit(CAPABILITY_HW_CRYPTO, &rt2x00dev->cap_flags) && rt2x00dev->mfprequested) {
>>>> + INFO(rt2x00dev, "802.11w support (MFP) enabled.\n");
>>>> + rt2x00dev->hw->flags |=
>>>> + IEEE80211_HW_MFP_CAPABLE;
>>>> + }
>>>
>>> Can't the whole patch be simplified into
>>>
>>> if (!test_bit(CAPABILITY_HW_CRYPTO, &rt2x00dev->cap_flags)) {
>>> INFO(rt2x00dev, "802.11w support (MFP) enabled.\n");
>>> rt2x00dev->hw->flags |=
>>> IEEE80211_HW_MFP_CAPABLE;
>>> }
>>
>> This would surely be possible, but it wouldn't be possible any more to
>> run the driver w/o MFP support as long as hw encryption is disabled.
>>
>> Additionally, I would like to have an additional comment added to
>> nohwcrypt, which mentions, that activating nohwcrypt enables MFP, like:
>> "Disable hardware encryption, enable MFP." to let the user know, how to
>> enable MFP.
>
> I am wondering what the usecase would be for having an option to disable MFP?
> Isn't that a feature which technically should be enabled by default and in the
> userspace you have the configuration to use it or not?
It's the same idea as behind the nohwcrypt switch. If there are problems
with the feature in a special case, you have the possibility to disable it.
My understanding of nohwcrypt is to have a fallback mode, which I didn't
want to touch. That's all.
Regards,
Andreas
next prev parent reply other threads:[~2012-05-10 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 7:19 [PATCH][RFC/RFT] rt2800: Implement selectable support for 802.11w (MFP) Andreas Hartmann
2012-05-10 8:58 ` [rt2x00-users] " Ivo Van Doorn
2012-05-10 10:55 ` Andreas Hartmann
2012-05-10 12:34 ` Ivo Van Doorn
2012-05-10 14:21 ` Andreas Hartmann [this message]
2012-05-10 14:47 ` Gertjan van Wingerde
2012-05-10 15:32 ` Andreas Hartmann
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=4FABCECC.30709@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).