Hi, We are also trying to understand the transmission path of the data packets when it goes through the ath5k driver. We tried sending data out from the system using ping and iperf. We were trying to print the 802.11 MAC header in the ath5k_tx_queue() in base.c. But when we tried running iperf/ping from the system, in the kernel log only showed the HEX values for Frame Control field as 0188 which are Association requests. Here the duration field was 0000.
Now we are confused on why are we not able to find any Data frames OR RTS/CTS control frames when we do iperf/ping. I would be very thankful if someone can tell the reason behind so and explain some basics where I might be missing. Also the way we are trying to test things are appropriate or we should be doing this in some different way ? Our basic reason behind doing this is, we are trying to understand the 802.11 implementation with ath5k driver and we will try to analyze the performance difference if we make some changes. Thanks, PeeyushPD
_______________________________________________ ath5k-devel mailing list ath5k-devel@lists.ath5k.org https://lists.ath5k.org/mailman/listinfo/ath5k-devel
