From: Johannes Berg <johannes@sipsolutions.net>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection
Date: Fri, 12 Dec 2008 23:37:46 +0100 [thread overview]
Message-ID: <1229121467.3565.2.camel@johannes.berg> (raw)
In-Reply-To: <69e28c910812121432k1e8732bcma77e489d247ecdf4@mail.gmail.com> (sfid-20081212_233239_864570_76D3B7E9)
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Fri, 2008-12-12 at 23:32 +0100, Stefanik Gábor wrote:
> Userspace packet injector applications might want to transmit packets
> that are, by design, not supposed to be acked. In other cases, an
> injector application may need to control the sequence number of the
> packets it transmits. Introduce 2 new flags in the "TX flags" Radiotap
> fields, controlling these 2 behaviors.
>
> The new fields are as follows:
>
> * IEEE80211_RADIOTAP_TX_FLAGS
>
> IEEE80211_RADIOTAP_F_TX_NO_ACK: Transmit the packet once with no waiting for
> an ACK and no retrying if no ACK received
> IEEE80211_RADIOTAP_F_TX_NO_SEQ: Use the sequence number already present in
> the 802.11 header, do not generate a new one
> in the driver/stack. Useful when injecting
> fragments with the same sequence number.
Umm, these aren't really defined by radiotap yet. Does all of this have
to be NOW?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-12-12 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 22:32 [RFC 0/3] cfg80211, mac80211: Introduce radiotap flags for finer userspace control of injection Stefanik Gábor
2008-12-12 22:37 ` Johannes Berg [this message]
2008-12-12 22:40 ` Stefanik Gábor
2008-12-12 22:42 ` Johannes Berg
2008-12-12 22:50 ` Johannes Berg
2008-12-12 22:54 ` Stefanik Gábor
2008-12-12 22:57 ` Johannes Berg
2008-12-13 0:20 ` Richard Farina
2008-12-13 0:26 ` Johannes Berg
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=1229121467.3565.2.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@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