> There's no easy way to do tx ack reporting on the rtl8187. This also means it doesn't show you outgoing frames on a monitor. We really need to find a solution here that takes into account our current use of tx status reports for outgoing frame monitor as well as rate control. At the higher network speeds of 802.11n equipment we'll not want to do this anyway. Since hostapd needs to know whether the packets it sent were acked, we'll have to go back to using IEEE80211_TXCTL_REQ_TX_STATUS for those injected frames. Then we need to decide whether we want to report all outgoing frames on monitor interfaces or only those where the hardware was able to provide a status report. The latter would be sufficient for hostapd, of course. Finally, we need to create a new hardware flag that determines whether the driver will report status for all frames or not, this influences the possible rate control algorithm choices. Of course we still need to write rate control algorithms that are able to work with synthesized information... johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
