From: Johannes Berg <johannes@sipsolutions.net>
To: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Cc: linux-wireless@vger.kernel.org, technoboy85@gmail.com
Subject: Re: [PATCH]: setting bit-rate when injecting
Date: Mon, 09 Nov 2009 17:50:22 +0100 [thread overview]
Message-ID: <1257785423.29454.177.camel@johannes.local> (raw)
In-Reply-To: <f74418680911090807g4e83a15cr2ce21ea21a86ea23@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
On Mon, 2009-11-09 at 17:07 +0100, Lorenzo Bianconi wrote:
> I and my Matteo Croce made a patch which adds the capability
> to set the bit-rate when injecting in monitor mode.
>
> The code parse the bit-rate field from the radiotap header and passes the info
> to the struct ieee80211_tx_info
>
> --- a/net/mac80211/tx.c 2009-11-09 16:41:15.000000000 +0100
> +++ b/net/mac80211/tx.c 2009-11-09 16:50:12.000000000 +0100
> @@ -505,6 +505,9 @@
> struct ieee80211_tx_rate_control txrc;
> u32 sta_flags;
>
> + if (info->control.vif->type == NL80211_IFTYPE_MONITOR)
> + return TX_CONTINUE;
Sorry, can't do that, we need rate control for packets that are injected
from hostapd.
> - int ret = ieee80211_radiotap_iterator_init(&iterator, rthdr, skb->len);
> + int i, ret = ieee80211_radiotap_iterator_init(&iterator,
> + rthdr, skb->len);
> + struct ieee80211_rate *rates;
A separate "int i;" would be a lot cleaner I think.
> sband = tx->local->hw.wiphy->bands[tx->channel->band];
>
> @@ -979,6 +984,25 @@
> tx->flags |= IEEE80211_TX_FRAGMENTED;
> break;
>
> + case IEEE80211_RADIOTAP_RATE:
> + rates = sband->bitrates;
> + for (i = 0; i < sband->n_bitrates; i++) {
> + if (rates[i].bitrate/5 == *iterator.this_arg) {
> + info->control.rates[0].idx = i;
> + break;
> + }
> + }
> + info->control.rates[0].flags = 0;
This leaves the number of retries at ... 0. That makes no sense. What
driver are you using that this actually works with?!
> @@ -1518,7 +1542,6 @@
> struct net_device *dev)
> {
> struct ieee80211_local *local = wdev_priv(dev->ieee80211_ptr);
> - struct ieee80211_channel *chan = local->hw.conf.channel;
> struct ieee80211_radiotap_header *prthdr =
> (struct ieee80211_radiotap_header *)skb->data;
> struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
> @@ -1540,9 +1563,6 @@
> * radar detection by itself. We can do that later by adding a
> * monitor flag interfaces used for AP support.
> */
> - if ((chan->flags & (IEEE80211_CHAN_NO_IBSS | IEEE80211_CHAN_RADAR |
> - IEEE80211_CHAN_PASSIVE_SCAN)))
> - goto fail;
We don't want to break regulatory rules either ...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-11-09 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 16:07 [PATCH]: setting bit-rate when injecting Lorenzo Bianconi
2009-11-09 16:34 ` John W. Linville
2009-11-09 16:50 ` Johannes Berg [this message]
2009-11-09 17:14 ` Matteo Croce
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=1257785423.29454.177.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=technoboy85@gmail.com \
/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