From: "Hakan Coşkun" <hakanberlin@gmail.com>
To: <linux-wireless@vger.kernel.org>
Subject: Re: Frame Injection with NL80211_CMD_FRAME is failing (SOLVED)
Date: Fri, 17 Oct 2014 16:52:15 +0200 [thread overview]
Message-ID: <D066F86F.F9DA%hakanberlin@gmail.com> (raw)
Hi all,
I found the problem. There is a check in /net/mac80211/cfg.c
!rcu_access_pointer(sdata->bss->beacon))
I guess this related to beaconing. If it is not configured, off-channel is
required in any case.
If you put the interface into AP mode and try to send frames with
NL80211_CMD_FRAME you have to set the OFFCHANNEL_TX_OK flag in any case !!!
Right now I am facing the problem of not getting probe-requests delivered
to my master mode interface through NL80211_CMD_REGISTER_FRAME. It works
only if I start an additional monitor interface on the same card. Any clue
what to do to enable frame delivery to the AP interface without a monitor
interface.
Kind Regards,
Hakan
Am 03.10.14 12:04 schrieb "Hakan Coşkun" unter <hakanberlin@gmail.com>:
>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-17 14:52 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=D066F86F.F9DA%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).