From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k: injecting frames at a rate other than 1Mbps
Date: Tue, 02 Mar 2010 22:45:20 -0500 [thread overview]
Message-ID: <1267587920.30055.1.camel@mj> (raw)
In-Reply-To: <40101cc31003021325w4d65f116g6711b2d60cb66ff9@mail.gmail.com>
On Tue, 2010-03-02 at 22:25 +0100, rootkit85 at yahoo.it wrote:
> Do you inject from userspace or kernelspace?
> How do you know that they are sent at 1 Mbit? Do you sniff from another pc?
> My patch was tested only with kernelspace injection, feedback is welcome.
I think that part is wrong:
+ if (sband->bitrates[i].bitrate <=
+ *iterator.this_arg * 5) {
+ info->control.rates[0].idx = i;
+ break;
+ }
If a bitrate is less than the requested one, it would still match.
I think we should require an exact match. Requests to use an
unsupported rate should result in dropping the packet. That applies to
rate 0 as well, unless there is a special interpretation in the
standard. I don't see any: http://www.radiotap.net/defined-fields/Rate
I tried the part of you patch that handles IEEE80211_RADIOTAP_RATE, but
it still would not work. It turns out the rate control would override
the rate. I don't see an easy way to prevent it short of introducing
another flag.
I've made an alternative patch and I'll submit it to linux-wireless
shortly. It actually works for userspace injection.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-03-03 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 20:00 [ath9k-devel] ath9k: injecting frames at a rate other than 1Mbps Andrew Watts
2010-03-02 21:25 ` rootkit85 at yahoo.it
2010-03-03 3:45 ` Pavel Roskin [this message]
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=1267587920.30055.1.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.