From: Ronald Linders <r.f.a.linders@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: New type of action frame is not passed on to user space
Date: Mon, 27 Mar 2017 14:37:30 +0200 [thread overview]
Message-ID: <CADGSyv6f=16a+-VE++b5XdKUbm525Cb_4HoG0RMub_ZzL4HCDw@mail.gmail.com> (raw)
Hi all,
Currently I'm working on an implementation of a new draft Wi-Fi
standard, which offers a solution for device authentication. In this
new protocol action frames are specified, similar to those for
peer-to-peer, but with a different OUI type (0x1a). In user space
(nl80211 driver) I have registered this new type of action frame
similar as has been done for peer-to-peer action frames (
nl80211_register_action_frame(bss, (u8 *) "\x04\x09\x50\x6f\x9a\x1a",
6) ).
To let a device sending this new action frame is no problem (seen on a
wifi-sniffer), but on the receiving device no event is generated that
the action frame has arrived.
However, if I only change the OUI type into 0x9, making it a P2P
action frame, the receving device IS generating an event on reception,
Somehow it seems that the kernel driver is discarding my newly defined
action frame (and any other unknown frame for that matter) and
therefore is not passing it to wpa_supplicant although I have
registered the new frame there.
My set-up consists of 2 Nexus 5x smartphones (Android 7.1.1 AOSP)
interacting with eachother via Wi-Fi. These smartphones have a
Qualcomm QAC6174 Wi-Fi chip.
Is someone able to give me a clue how I can instruct the kernel driver
to pass me the new action frame type to user space on arrival?
Any help is highly appreciated.
With kind regards,
Ronald Linders
reply other threads:[~2017-03-27 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADGSyv6f=16a+-VE++b5XdKUbm525Cb_4HoG0RMub_ZzL4HCDw@mail.gmail.com' \
--to=r.f.a.linders@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).