On Tuesday 02 March 2010 18:42:38 Jouni Malinen wrote: > On Tue, Mar 02, 2010 at 11:51:58AM +0900, Bruno Randolf wrote: > > injected frames have to use AR5K_PKT_TYPE_NORMAL, otherwise the hardware > > thinks it can mess with the contents of the frame - e.g. update the TSF > > of an injected beacon. injected frames should be sent as they are > > provided. > > Why would we never want the hardware to update fields in injected > frames? Unless I missed something, this seems to break hostapd use cases > where the hardware is indeed expected to update the timestamp in Probe > Response frames and set up seq# and duration etc. as appropriate for the > frames (the latter may be driver/mac80211 work; the timestamp needs to > come from hardware/firmware).
ok, i see. > If we want to have an option to prevent hardware from touching the frame > payload, that really should be an option (a radiotap and TX control > flags, etc.), not default functionality for monitor interface. The use > case for this seems to be some kind of testing purpose and that should > not really break more common functionality. yes, we use it for testing IBSS mode (merging, TSF updates) by injecting custom beacons. i guess other packet injectors would also assume that their packets go out untouched. so what would be a way to support that properly? what about a monitor mode flag? bruno _______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
