Hello Sir!
Seeing as you are the author of the drivers that make the D-Link DWL-G122 work so well under BACKTRACK, I was hoping you wouldn't mind me asking a question here!! I was always getting the "-1" signal strength problem when I was injecting because (apparently) of the prism headers in the drivers that came pre-installed with Backtrack. I have upgraded to your drivers and most things seem to work well - injecting etc etc are perfect and I can get WEP keys fairly easily.
However over on the BACK TRACK fourms an interesting problem has appeared with sending DEAUTH packets with the D-LINK. Here's a snippet from a guy called "bigcat99":
I've tried both of the instructions for the DWL-G122 B1, and when I run the "injection test" I only get malformed packets. I've got the DWL-G122 B1 and here's what I do...
1: after boot is done insert card
2: airmon-ng start
3: airodump-ng rausb0
4: aireplay -0 10 -a 01:02:03:04:05:06 rausb0
5: launch wireshark (ethereal) and look for deauth packets.
This always gives malformed packets.
I've double checked this myself and it certainly does screw up DEAUTH packets. They all appeared malformed.
Then recently he discovered that:
airmon-ng start
iwpriv rausb0 rfprismhdr 0airodump-ng rausb0
aireplay-ng -0 100 -a 11:22:33:44:55:66 rausb0
Open Wireshark - and OMG there they are - deauth frames
Looking on the driver page -
http://homepages.tu-darmstadt.de/~p_larbig/wlan/Only difference is, that the official one is still doing automatic prism header switching, which is annoying, but can be disabled via an iwpriv command now.
Anyway, hope this helps someone cos its been driving me crazy all day.. I guess that the "rfprismhdr" is set to "1" by default when the driver starts, and that this is causing the hassle ?
I've made a quick video of all of this (under 2mins) which you can see here:
http://rapidshare.com/files/5632271/errorheaders.avi which explains this better than me rambling on. Seeing as you seem to know so much more about these headers than I will ever do, would you have any advice/explaination or even fixes for the drivers to send proper packets.
It seems that as soon as I do the " iwpriv rausb0 rfprismhdr 0 " the signal problem of "-1" starts again

.