On Thu, May 22, 2008 at 10:09 PM, JMF <tolas_feup@xxxxxxxxxxx> wrote: > Johannes Berg <johannes@...> writes: > >> >> > >> This does not work, since we use injection for other types of >> > >> frames. For example management frames from hostapd. We don't want >> > >> (and can't) make hostapd keep track of sequence numbers. >> > >> You'll have to contact radiotap people and add a flag for this. >> > >> This would also solve the hardware counter problem then. >> >> > The flag is IEEE80211_TX_INJECTED. Here is a new patch, for the >> > current wireless-testing: > > > Are you really sure the flag is IEEE80211_TX_INJECTED? > For the current (today, 22 May) wireless-testing, it seems it's been > renamed to IEEE80211_TX_CTL_INJECTED. Also, not tx->flags anymore, but > info->flags instead. > Can you confirm that? > > > I was going to say something else, but I saw another post by Johannes... Strange > that hostapd uses injection in monitor mode interfaces, I thought it would be > only AP mode interfaces. > And it is also strange that iwlwifi developers wanted to disallow injection in > monitor mode, with hostapd apparently needing it! On behalf of iwlwifi, this is legacy behavior that wasn't treated for a,b,c reasons. There used to be management interface that was used by hostapd and monitor interface was used for sniffing. So with wanting or not wanting it is actually all around. Tomas > > -- > 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 > -- 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
