If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Exactly why were you unsuccessful using the drivers from the repository? You do not need to manually compile and install r8187 driver by hand as it is not the easiest thing for beginners. I have written up a guide on my blog which sort of used to work prior to me contacting muts in regards to having the driver to be packaged and placed into the repository.

First things first, once you have installed r8187-drivers, you need to unplug the device (after ifconfig it down of course), blacklist rtl8187 and then make sure there's no traces of rtl8187 and its deps are in the lsmod (provided that you have only one wireless device) and then you plug the device back in.

My personal blog is here but I highly recommend you to not follow the guide on my blog as it is not easy for beginners.

Exactly why were you unsuccessful using the drivers from the repository? You do not need to manually compile and install r8187 driver by hand as it is not the easiest thing for beginners. I have written up a guide on my blog which sort of used to work prior to me contacting muts in regards to having the driver to be packaged and placed into the repository.

First things first, once you have installed r8187-drivers, you need to unplug the device (after ifconfig it down of course), blacklist rtl8187 and then make sure there's no traces of rtl8187 and its deps are in the lsmod (provided that you have only one wireless device) and then you plug the device back in.

My personal blog is here but I highly recommend you to not follow the guide on my blog as it is not easy for beginners.

Because when I use the command given, it does not work. I have gone through synaptic as well but have found nothing. I will look at your blog.

Thanks,
red

Edit:
A tutorial is a tutorial, if all commands are listed correctly, anyone can follow. Yours is very similar to the post on aircrack making it a piece of cake. Thank you for giving me the link and making the tutorial. I will report if there are any errors.

Edit2:
Worked beautifully, thank you very much. I also bookmarked your blog. =) Last but not least, when I use airmon-ng, it does not create vap's like the previous driver did, such as mon0, mon1, and etc. Now, it goes into monitoring mode, but does not create them.

Last but not least, when I use airmon-ng, it does not create vap's like the previous driver did, such as mon0, mon1, and etc. Now, it goes into monitoring mode, but does not create them.

Yes, that's one of the main differences between the mac and ieee drivers.

That's not the main difference between mac80211 and ieee80211 drivers, that's just an extra interface created specifically for monitoring and what not. It is not a mandatory option to use airmon-ng as I believe it can confuse the living hell out of most people. I still would recommend the usage of iwconfig <dev> mode monitor

Moreover, the real difference between mac80211 and ieee80211 drivers are the lack of needing to use extra tools. Users of atheros, aironet, prism2_usb would know what I mean.

VAP was an unique thing for atheros owners (using madwifi-ng) but at the same time it confused many people, such as the fact you cannot simply do iwconfig ath0 mode monitor, you need to destroy the VAP (well preferrably) and create a new one specifically for monitoring. That wasn't a real drawback considering it was in theory possible to setup an AP and monitor on the same channel.