Johannes Berg wrote:
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?
Is there a compelling reason to prohibit progress?
--Rick
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
