From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Denis Kenzior <denkenz@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v7 00/11] EAPoL over NL80211
Date: Tue, 27 Mar 2018 22:51:11 +0200 [thread overview]
Message-ID: <5ABAAEBF.6080900@broadcom.com> (raw)
In-Reply-To: <00fa528f-5c5e-1263-b058-317de71ee769@gmail.com>
On 3/27/2018 4:42 PM, Denis Kenzior wrote:
> Hi Arend,
>
> On 03/27/2018 03:03 AM, Arend van Spriel wrote:
>> On 3/26/2018 7:52 PM, Denis Kenzior wrote:
>>> The proposed patchset has been tested in a mac80211_hwsim based
>>> environment with
>>> hostapd and iwd.
>>
>> Hi Denis,
>>
>> Looking pretty good. Do you also have hostapd and iwd patches
>> available somewhere. I would like to see if I can get brcmfmac using it.
>>
>
> There are some very raw iwd patches I have. They're sitting in my
> private tree. I can send these to you privately or maybe setup a wiki
> page somewhere for you to grab them. They do not take the
> NL80211_EXT_FEATURE_CONTROL_PORT_OVER_NL80211 feature bit into account,
> so I still need to work on these. Was holding off until Johannes merges
> at least the high level API bits.
If they are not fit for posting feel free to send them to me.
> I never modified hostapd. iwd has a very rudimentary AP mode support.
> Not fully useable but enough to run a 4-way handshake. So with that in
> mind I concentrated on two scenarios while testing:
>
> 1. modified iwd (STA) utiling EAPoL over NL80211 connecting to stock
> hostapd. In effect this was testing both the legacy and the new behavior.
>
> 2. modified iwd (STA) utilizing EAPoL over NL80211 connecting to stock
> hostapd. Then disconnecting and connecting to modified iwd (AP).
>
> iwd doesn't (yet) have support for P2P, IBSS or Mesh. So the bits
> touching these features should be considered untested.
That's fine. Just wanted to get a feel about the feature. May provide
some lessons to try it with a non-mac80211 driver and I wanted to have a
spin with iwd as that is new to me.
Regards,
Arend
next prev parent reply other threads:[~2018-03-27 20:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 17:52 [PATCH v7 00/11] EAPoL over NL80211 Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 01/11] nl80211: Add CMD_CONTROL_PORT_FRAME API Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 02/11] nl80211: Implement TX of control port frames Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 03/11] nl80211: Add CONTROL_PORT_OVER_NL80211 attribute Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 04/11] cfg80211: Support all iftypes in autodisconnect_wk Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 05/11] nl80211: Add SOCKET_OWNER support to JOIN_IBSS Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 06/11] nl80211: Add SOCKET_OWNER support to JOIN_MESH Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 07/11] nl80211: Add SOCKET_OWNER support to START_AP Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 08/11] nl80211: Add control_port_over_nl80211 for ibss Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 09/11] nl80211: Add control_port_over_nl80211 to mesh_setup Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 10/11] mac80211: Add support for tx_control_port Denis Kenzior
2018-03-26 17:52 ` [PATCH v7 11/11] mac80211: Send control port frames over nl80211 Denis Kenzior
2018-03-27 8:03 ` [PATCH v7 00/11] EAPoL over NL80211 Arend van Spriel
2018-03-27 14:42 ` Denis Kenzior
2018-03-27 20:51 ` Arend van Spriel [this message]
2018-03-29 12:44 ` Johannes Berg
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=5ABAAEBF.6080900@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=denkenz@gmail.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;
as well as URLs for NNTP newsgroup(s).