From: Markus Theil <markus.theil@tu-ilmenau.de>
To: Johannes Berg <johannes@sipsolutions.net>,
Denis Kenzior <denkenz@gmail.com>, Jouni Malinen <j@w1.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] Revert "mac80211: support NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211_MAC_ADDRS"
Date: Wed, 11 Mar 2020 10:36:02 +0100 [thread overview]
Message-ID: <4d366e81-d523-d23b-cbf9-2d118a2b77e6@tu-ilmenau.de> (raw)
In-Reply-To: <f230965a23ee69341a402dff15efb67c7c221bde.camel@sipsolutions.net>
On 11.03.20 10:31, Johannes Berg wrote:
> On Wed, 2020-03-04 at 17:24 +0100, Markus Theil wrote:
>
>> Is there any consensus on how to move on in this discussion? In my
>> opinion a pragmatic way would be to make rx forwarding of pre-auth
>> frames optional with a flag which can be set whenever
>> NL80211_ATTR_CONTROL_PORT_OVER_NL80211 is included, like Denis has
>> already proposed. We could call this flag for example
>> NL80211_ATTR_CONTROL_PORT_NO_PREAUTH.
> Yeah, that seems right.
>
> Do you want to make the patch?
Yes, I have already some code lying around for it, but did not have time
to test them.
> johannes
>
prev parent reply other threads:[~2020-03-11 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 9:19 [PATCH 1/2] Revert "mac80211: support NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211_MAC_ADDRS" Johannes Berg
2020-02-24 9:19 ` [PATCH 2/2] Revert "nl80211: add src and dst addr attributes for control port tx/rx" Johannes Berg
2020-02-24 16:56 ` [PATCH 1/2] Revert "mac80211: support NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211_MAC_ADDRS" Denis Kenzior
2020-02-24 18:26 ` Johannes Berg
2020-02-24 18:26 ` Denis Kenzior
2020-02-24 18:47 ` Johannes Berg
2020-02-24 18:57 ` Denis Kenzior
2020-02-24 19:34 ` Johannes Berg
2020-02-24 19:35 ` Denis Kenzior
2020-02-25 11:00 ` Jouni Malinen
2020-02-25 17:06 ` Denis Kenzior
2020-03-04 16:24 ` Markus Theil
2020-03-11 9:31 ` Johannes Berg
2020-03-11 9:36 ` Markus Theil [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=4d366e81-d523-d23b-cbf9-2d118a2b77e6@tu-ilmenau.de \
--to=markus.theil@tu-ilmenau.de \
--cc=denkenz@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--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