search

snowflakekiller / wifite

Automatically exported from code.google.com/p/wifite
GNU General Public License v2.0
0 stars 0 forks source link

unknown error 132 #33

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.
hi all i use w7+vmware newest+ bt4 r1+rtl 8187 external router
and i have  in monitor mode unknown error 132
samone can help me ho can make it?ty bro

Original issue reported on code.google.com by gothi...@gmail.com on 10 Nov 2010 at 9:09

GoogleCodeExporter commented 9 years ago 
Hello gothicLv, i was searching for some things when i came across with your 
question. Look, i'm using the ALFA AWUS036H usb adapter for access to wifi. The 
chipset of the ALFA is ''rtl8187'' (as yours). so, after a long search and 
having the same problem with you, i found the solution about this ''unknown 
error 132''.. all you have to do is to get rid of ''VMware'' and start using 
live-cd.. so, you have to download the backtrack to the .iso format and burn it 
to a dvd, so that you create what we call live-cd. then you are going to put in 
your live-cd and reboot.. now you will boot from this cd and you are going to 
use bactrack.. then you will notice that when you type in ''armon-ng start 
(wlan0 or ath0 etc.)'' you won't have anymore ''unknown error 132''.. 
I hope all these will help you.. :D

Original comment by giannis_...@hotmail.com on 15 Nov 2010 at 12:44

GoogleCodeExporter commented 9 years ago 
Look At this page 
http://www.backtrack-linux.org/wiki/index.php/Rtl8187_vs_r8187 from BackTrack 
it works with any linux out there. For some reason its a rfkill that blocks the 
radio frequenzy and shuts it off.

Original comment by cure.my....@gmail.com on 6 Jan 2011 at 10:58

GoogleCodeExporter commented 9 years ago 
I *could* write a work-around to unload/reload the drivers to solve this issue, 
but having a python script automatically load/unload drivers seems... dangerous.

I think it's best if you guys (the users) check that rfkill hasn't turned off 
wireless radio.

I'm marking this was WontFix; hope you guys understand...

Original comment by der...@gmail.com on 19 Jan 2011 at 3:30