From: "Hakan Coşkun" <hakanberlin@gmail.com>
To: <linux-wireless@vger.kernel.org>
Subject: Frame Injection with NL80211_CMD_FRAME is failing
Date: Fri, 03 Oct 2014 12:04:09 +0200 [thread overview]
Message-ID: <D0544139.F308%hakanberlin@gmail.com> (raw)
Hi,
For some time I am playing around with tools like scapy, senf, lorcon etc.
Which allow to receive and construct frames in user-space and send them
with
pcap or raw sockets. I am trying to achieve the injection part with
NL80211_CMD_FRAME. According to the description, only management frames are
supported by this command. Am I right ?
I put some printks into nl80211.c and mlme.c to follow the transmission
part
and to understand where my commands are failing.
I¹ve put my interface into master mode (NL80211_IFTYPE_AP) in order pass
the
checks in cfg80211. When I try to send down a beacon frame or another
management frame I got an error from cfg80211_mlme_mgmt_tx in mlme.c.
rdev_mgmt_tx returns an error code. How can I figure out why my frame is
not
send down on the wiphy ?
By the way, why is CMD_FRAME only restricted to management frames ?
Regards,
Hakan
reply other threads:[~2014-10-03 10:04 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=D0544139.F308%hakanberlin@gmail.com \
--to=hakanberlin@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).