From: bruno randolf <bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Cc: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Subject: Re: IEEE80211_RADIOTAP_DATA_RETRIES for tx frames?
Date: Thu, 29 Nov 2007 12:48:03 +0900 [thread overview]
Message-ID: <200711291248.03254.bruno@thinktube.com> (raw)
In-Reply-To: <20071128031558.GQ3568-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
On Wednesday 28 November 2007 12:15:58 David Young wrote:
> On Wed, Nov 28, 2007 at 11:27:59AM +0900, bruno randolf wrote:
> > hello!
> >
> > while working on packet injection for madwifi i came across the following
> > question:
> >
> > can we use the IEEE80211_RADIOTAP_DATA_RETRIES for injected TX frames to
> > specifiy the number of retries to be used?
> >
> > this usage seems to be slighty different from the strict specification of
> > radiotap for this field (at least the version of the header we have
> > included in madwifi now) because it was concerned with received data
> > frames only, and we apply it to all kinds of frames to be TXed:
> >
> > /*
> > * IEEE80211_RADIOTAP_DATA_RETRIES u_int8_t data
> > *
> > * Number of unicast retries a transmitted frame used.
> > */
> >
> > could we extend the meaning of this field to be applicable to transmit
> > frames too?
>
> I think that we should. I intend to use it that way, myself.
thanks dave!
i commited code to the madwifi svn which does that now.
bruno
prev parent reply other threads:[~2007-11-29 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 2:27 IEEE80211_RADIOTAP_DATA_RETRIES for tx frames? bruno randolf
[not found] ` <200711281127.59233.bruno-L9ZBdB2wSWtl57MIdRCFDg@public.gmane.org>
2007-11-28 3:15 ` David Young
[not found] ` <20071128031558.GQ3568-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-11-29 3:48 ` bruno randolf [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=200711291248.03254.bruno@thinktube.com \
--to=bruno-l9zbdb2wswtl57midrcfdg@public.gmane.org \
--cc=dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
--cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.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.