*I am a newb to Linux/Backtrack. (Thus why I am posting in the Newbie Area)
*I am using a LiveCD.
*I have read EVERY thread on IPWraw drivers and WEP Cracking [multiple times]
*I have installed the IPWraw drivers and it is working [to the best of my knowledge]
*I'm trying to crack my 128bit WEP Key. I have successfully done it already two times, but not by injecting (I had a friend download a big file to generate IV's(?), and once it hit around 300k I cracked the key with Aircrack-ng in about 30 seconds(!) each time)
Here are the commands that I use and the errors I get (when I try to crack it with clients):
[EVERYTHING WORKS FINE HERE]Code:airodump-ng -i -w /tmp/wepkeys -c 6 --bssid BSSID wifi0
[I get ARP requests and send packets eventually, but doesCode:aireplay-ng wifi0 --arpreplay -b BSSID -h MYMAC
Notice: got a deauth/disassoc packet. Is the source MAC associated ?]
"NB: this attack is more effective when targetingCode:aireplay-ng wifi0 --deauth 10 -a CLIENT
a connected wireless client (-c <client's mac>)."
04:00:45 Sending DeAuth to broadcast -- BSSID: [CLIENT]
04:00:46 Sending DeAuth to broadcast -- BSSID: [CLIENT]
04:00:47 Sending DeAuth to broadcast -- BSSID: [CLIENT]
and so on...
But my problem is that in airodump it's like this:
See where the 560046 is, well, shouldn't that be up on the top row and not down there on the 2nd row of stuff? Why don't I have alot of IV's on top, but have tons on the bottom?Code:BSSID PWR RXQ Beacons #Data... 00:00:00:00:00:00 -1 100 123216 2891 BSSID STATION PWR Lost Packets 00:00:00:00:00:00 00:00:00:00:00:00 -1 51 2179 00:00:00:00:00:00 00:00:00:00:00:00 -1 49473 560046
Sorry for the supernewb question, yall. I've searched, but couldn't find the answer
Thanks for the help!
Μολὼν λαβέ - Great spirits encounter heavy opposition from mediocre minds.
Code:enhanced driver by aspj New in ipwraw-ng 2.0.0: * Changed Makefile - 'make install' tries to find installed firmware and check version; 'make install_ucode' installs firmware 2.14.4 (included with the source code) * Applied Ian's patch. This basically updates the driver to use the new "unify" ucode (which is used also by iwlwifi 0.0.33+), fixes some bugs, and makes it easier to port new bugfixes * rtap interface is created by default after a 'modprobe ipwraw'
Watch your back, your packetz will belong to me soon... xD
BackTrack : Giving Machine Guns to Monkeys since 2006
Thank yall both very much!Code:cd /tmp mv ipwraw-ng.lzm.bz2 ipwraw-ng.lzm lzm2dir ipwraw-ng.lzm / cd /tmp/ipwraw make make install /usr/src/drivers/ipw3945-1.2.0/unload /tmp/ipwraw/load
Ok, I changed some of the above commands for the install to fit this one (I think). And I think it installed it, but when I try to load it, it says:
Do you know what I did wrong?Code:Unloading ipwraw...done Loading ipwraw...done Waiting for /sys/class/net/wifi0/device/rtap_iface to appear...time out. Could not find wifi0 interface
Here's how I "installed" it
then I get the error I postedCode:I opened the .tar file and copied and pasted the folder "ipwraw-ng" into my /tmp directory cd /tmp/ipwraw-ng make make install ["you can install the firmware using "make install_ucode" and "you can load the module with "modprobe ipwraw"] so I type in "make install_ucode" Installing ucode in /lib/firmware...done then type in "modprobe ipwraw" "load"
Know what I did wrong?
I got Kismet to work with ipw3945
After adjusting the KISMET.conf file to:
My firmware was 2.14.3 (what was said after make install)Code:source=ipw3945,eth1,intel
So I used
now the new make install says that version 2.14.4 is adequate.Code:make install_unicode
After killing ipw3945 and unloading it via modprobe.
When I start KISMET I get following errorCode:/usr/src/drivers/ipw3945-1.2.0/unload modprobe -r ipw3945
FATAL: GetIFFlags: interface eth1: No such device
So I've adjusted the KISMET.conf file to:
Now I get the error:Code:source=ipw3945,rtap0,intel,1
FATAL: channel get ioctl failed 95:Operation not supported
after starting iwconfig, I noticed a wifi0 that was unassociated.
Now I've adjusted the KISMET.conf file to:
Now Kismet works with the ipwraw... I don't know about the packet injection, but i'll let you know.Code:source=ipw3945,wifi0,intel
ifconfig wifi0 up > ifconfig wifi0 down > ifconfig wifi0 up
(and I think then)...
ifconfig rtap0 up
when you do an iwconfig and can see both wifi0 and rtap0, you're obviously in business.
***Also make sure you unload the other driver before loading ipwraw
dd if=/dev/swc666 of=/dev/wyze
Also... do you have the ucode installed?
dd if=/dev/swc666 of=/dev/wyze
Yeah, actually I get it installed and working [to a degree], but I still can't really inject packets. I know the 3945 is pretty sketchy, so I ordered a WGT11 (should be in today or tomorrow)
Thanks alot, yall!
I still have the same problems as the or. IPWraw drivers, maybes that's just how it's gonna be.