radiotap header used in packet injection on monitor mode
Hi,
In our internal tests we make use of monitor mode (on wireshark) for all the debugging, especially with security related issues (as packets are already decrypted).
As i am "injecting the packet on to the network" using a "simulator" built by own (very similar to the file2air) with the help of lorcon library, there we are setting the radiotap header as 14 bytes and writing the buffer on to the sockets and sending the frame.
But when the same frame is captured in wireshark is having different header length. Why is it happening so ?
Is it the problem in setting the radiotap header arguments in lorcon or what.
Thanks & Regards
Krama
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · krama
As i am "injecting the packet on to the network" using a "simulator" built by own (very similar to the file2air) with the help of lorcon library, there we are setting the radiotap header as 14 bytes and writing the buffer on to the sockets and sending the frame.
But when the same frame is captured in wireshark is having different header length. Why is it happening so ?
This is not the right list for such questions, and I see you've already posted to the Linux list(s) anyway.
johannes