From: Daniel Berger <daniel@dat-berger.de>
To: linux-wireless@vger.kernel.org
Subject: Manual Control about Sending ACKs
Date: Wed, 22 Sep 2010 12:36:28 +0200 [thread overview]
Message-ID: <20100922123628.61921924@danmob> (raw)
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
Hi,
im a Student in Germany currently working on a project concerning
wireless security.
For testing purposes we would like to send ACKs to packets, which
weren't adressed to us, or suppress sending normal ACKs.
I've looked through mac80211's code and found there much, what looks
like the ACK-sending-action is triggered in rx.c (we're checking CRC,
length, adressed to us, ...). But, one the other hand, tx.c states in a
comment
/* TODO: These control frames are not currently sent by
* mac80211, but should they be implemented, this function
* needs to be updated to support duration field calculation. *
[...]
* ACK: 0 if immediately previous directed data/mgmt had
* more=0, with more=1 duration in ACK frame is duration
* from previous frame minus time needed to transmit ACK
* and its SIFS
*/
Furthermore ath9k e.g. write parameters for configuring the sending of
ACKs direct into hw's memory...
Thus I deduce ACK sending is completely done in hardware.
Is this right? Is there any possible solution to my problem of sending
ACKs to
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-09-22 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 10:36 Daniel Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-22 10:39 Manual Control about Sending ACKs Daniel Berger
2010-09-22 13:02 ` John W. Linville
2010-09-22 13:45 ` Christian Lamparter
2010-09-22 13:54 ` Michael Büsch
2010-09-22 17:12 ` Luis R. Rodriguez
2010-09-22 17:17 ` Ben Greear
2010-09-22 18:38 ` Daniel Berger
2010-09-23 18:56 ` AW: " Bjoern Czybik
2010-09-23 20:14 ` Daniel Berger
2010-09-22 18:50 ` Nick Kossifidis
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=20100922123628.61921924@danmob \
--to=daniel@dat-berger.de \
--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).