Hi,
I have been using backtrack for a while and am testing the latest release, i have a physical install and when i try using injection using the above device it fails, if i switch the same device to the previous version of backtrack it works fine, has something changed or is this a known bug
AWUS036H with rtl8187l works out of the box for me.
You can use r8187 module to inject
rmmod rtl8187
modprobe r8187
airmon-ng start wlan0
airodump-ng wlan0 .........
for the rtl8187 module
airmon-ng start wlan0
write
iwconfig and you will
see a card mon0
then
airodump-ng mon0......
AWUS036H with rtl8187l works with me Im using BT 4 in VMware. Only problem with newist BT4 is that capturing WPA handshake takes a lot more time than in BT4 beta. There might be some updates, which can fix ur problem
you can blacklist the module you want doing this
echo "blacklist rtl8187" >> /etc/modprobe.d/blacklist
if you try to unload a module which is not loaded you will receive
i noticed all the days i use bt4f module r8187 works fine withERROR: Module rtl8187 does not exist in /proc/modules
open wep and wpa AP
so no reason to use rtl8187
rtl8187 also works fine with WEP and WPA, and it's loaded by default. Why saying that there is no reason to use rtl8187 driver if both drivers have the same performance?
Plus, rtl8187 uses the mac80211 stack, which is newer than ieee80211 (r8187). Here's an excerpt from aircrack-ng wiki that may help clarify the difference between the two stacks:
There is a new wireless stack starting in the mainline kernel since 2.6.22 called mac80211. As newer versions of the kernel get released more and more wireless devices are being supported by it. It has the huge advantage of being included in the kernel itself. The mac80211 stack has features such as software MAC (media access controller), hostapd, WEP, WPA, WME, a “link-layer bridging module,” and a QoS (quality of service) implementation. Of specific interest to aircrack-ng is native monitor mode and injection support.
The legacy drivers use the ieee80211 or net80211 stacks. And quite often there is one stack per wireless device. Depending on the driver, it does not provide native monitor mode or injection support.