Hi Arend,
On 01/03/2018 02:24 PM, Arend Van Spriel wrote:
On Tue, Jan 2, 2018 at 2:27 PM, Johannes Berg wrote:
On Fri, 2017-12-29 at 12:29 -0600, Denis Kenzior wrote:
Agreed, requiring both attributes is less than ideal, but I tried to
make the initial RFC as
On Tue, Jan 2, 2018 at 2:27 PM, Johannes Berg wrote:
> On Fri, 2017-12-29 at 12:29 -0600, Denis Kenzior wrote:
>
>> Agreed, requiring both attributes is less than ideal, but I tried to
>> make the initial RFC as minimal as possible. It also helped that iwd
>> uses
On Fri, 2017-12-29 at 12:29 -0600, Denis Kenzior wrote:
> Agreed, requiring both attributes is less than ideal, but I tried to
> make the initial RFC as minimal as possible. It also helped that iwd
> uses SOCKET_OWNER by default. What can be done is to always set
> conn_owner_nlportid and
On 12/29/2017 7:29 PM, Denis Kenzior wrote:
Hi Arend,
To make this possible this patchset introduces a new NL80211 command
and several
new attributes. A userspace that is capable of processing EAPoL
packets over
NL80211 includes a new NL80211_ATTR_CONTROL_PORT_OVER_NL80211
attribute in its
Hi Arend,
To make this possible this patchset introduces a new NL80211 command
and several
new attributes. A userspace that is capable of processing EAPoL
packets over
NL80211 includes a new NL80211_ATTR_CONTROL_PORT_OVER_NL80211
attribute in its
NL80211_CMD_ASSOCIATE or
On 12/28/2017 6:58 PM, Denis Kenzior wrote:
This patchset adds support for running 802.11 authentication mechanisms (e.g.
802.1X, 4-Way Handshake, etc) over NL80211 instead of putting them onto the
network device. This has the advantage of fixing several long-standing race
conditions that
This patchset adds support for running 802.11 authentication mechanisms (e.g.
802.1X, 4-Way Handshake, etc) over NL80211 instead of putting them onto the
network device. This has the advantage of fixing several long-standing race
conditions that result from userspace operating on multiple