A virtual machine is available here. See this page for more information.
A second, very light VMWare (15Mb required on disk) machine is available here. This machine currently only works with RT73. See this thread on the forum for more information.
I know that a lot of people are clamoring over Windows packet injection, since it's a nice thing to have if you don't want to run Linux. The only issue is that if you've got a PCI based card, and there are no Windows drivers, then there is no way to run such a device without rebooting into Linux.There are several reasons why this came about:- I don't want to mess with my host WLAN drivers. I also don't want to hack an RP-SMA connector into a $$$$ UMPC.- I needed something that would not require me to reboot in order to reset it- I didn't want to fool around with Commview (evaluation software) and or DLL's and stuff- I had a nice RT73 device with a RP-SMA connector on it from the factorySo, I set out to create a very small (sub 10MB) Virtual Appliance, primarily for VMware Player (freeware) under Windows, though it runs on Workstation and Fusion as well. This is the result.The appliance will boot up, and ask you to connect your RT73 device to the virtual machine if it can't find it, and then print a blurb about it's IP and a port number. Use these with the Aircrack suite on your HOST (not under the Virtual Machine- they aren't installed) instead of a device name. Aircrack & Friends will connect over IP to the Airserv-NG server running on the Virtual Machine, which will handle all passive monitoring and injection, segmented from the host (and thus this requires no drivers).I've included the Aircrack-0.9 SVN release for Windows in the file. You do NOT need to use Airserv-NG on the Windows side of things- it's automatically taken care of and launched inside the virtual machine.Requirements to run the virtual machine are pretty small:- 15MB of Hard Drive space- 64MB RAM (allocated to the VM)- Access to your USB ports (don't know how or if Vista handles that)- A USB RT73 device (I might support more in the future)- VMWare Player (Freeware - www.vmware.com)Just extract the archive, and ether doubleclick on the VMX file or open the VMX file in VMware Player. The appliance will boot. Attach the USB device using VMware Player's USB device list to the virtual machine (this will "grab" the USB device from the host OS, and attach it exclusively to the virtual machine). At this point the appliance will find the RT73 device, load the drivers, enable monitor and rfmontx modes, and launch Airserv-ng all automatically for you. Use the IP and Port Number that the appliance prints after it finishes booting (~30 seconds) with the Aircrack tools included instead of a device name.You can set VMware Player to poweroff the appliance when you exit- rather then suspending the appliance (which WILL mess things up). The appliance was built to clean-boot each time, and does not record data to the disk image (it runs off a ramdisk). You can just kill the appliance without running halt or poweroff (it does have a minimal shell). When you reboot it, it will reboot into a clean state each and every time.As usual, I'm not responsible for anything bad. I've tested the appliance with my own RT73 extensively on both my Mac running VMware Fusion, and my handheld OQO running VMware Player. In both cases I'm sure I looked like an idiot with a 6ft USB cable trailing attached to a handheld adapter/antenna/wand walking around with Airodump-NG running, but it worked just fine in both cases nevertheless. I did encounter one quirk with the VMware virtual machine dying, but it took me all of 35 seconds to reboot it to a clean state and I was off again.Let me know if something is broken. I'll try and find time to fix it, and maybe add more support for other USB devices in the future (though I'd probably publish those as their own appliance- to keep the size down, one appliance per USB adapter series/manufacture or something like that).I'd publish the source, but the appliance was built from a Gentoo development environment compiled specifically for this purpose (which is over 600mb in itself) of building embedded images. You can google TinyGentoo, which is what I used to build the appliance, along with many, many other modifications (primarily for Mdev firmware handling issues and a custom INIT script).
saurce: http://tinyshell.be/aircrackng/forum/index.php?topic=2204.0
A second, very light VMWare (15Mb required on disk) machine is available here. This machine currently only works with RT73. See this thread on the forum for more information.
I know that a lot of people are clamoring over Windows packet injection, since it's a nice thing to have if you don't want to run Linux. The only issue is that if you've got a PCI based card, and there are no Windows drivers, then there is no way to run such a device without rebooting into Linux.There are several reasons why this came about:- I don't want to mess with my host WLAN drivers. I also don't want to hack an RP-SMA connector into a $$$$ UMPC.- I needed something that would not require me to reboot in order to reset it- I didn't want to fool around with Commview (evaluation software) and or DLL's and stuff- I had a nice RT73 device with a RP-SMA connector on it from the factorySo, I set out to create a very small (sub 10MB) Virtual Appliance, primarily for VMware Player (freeware) under Windows, though it runs on Workstation and Fusion as well. This is the result.The appliance will boot up, and ask you to connect your RT73 device to the virtual machine if it can't find it, and then print a blurb about it's IP and a port number. Use these with the Aircrack suite on your HOST (not under the Virtual Machine- they aren't installed) instead of a device name. Aircrack & Friends will connect over IP to the Airserv-NG server running on the Virtual Machine, which will handle all passive monitoring and injection, segmented from the host (and thus this requires no drivers).I've included the Aircrack-0.9 SVN release for Windows in the file. You do NOT need to use Airserv-NG on the Windows side of things- it's automatically taken care of and launched inside the virtual machine.Requirements to run the virtual machine are pretty small:- 15MB of Hard Drive space- 64MB RAM (allocated to the VM)- Access to your USB ports (don't know how or if Vista handles that)- A USB RT73 device (I might support more in the future)- VMWare Player (Freeware - www.vmware.com)Just extract the archive, and ether doubleclick on the VMX file or open the VMX file in VMware Player. The appliance will boot. Attach the USB device using VMware Player's USB device list to the virtual machine (this will "grab" the USB device from the host OS, and attach it exclusively to the virtual machine). At this point the appliance will find the RT73 device, load the drivers, enable monitor and rfmontx modes, and launch Airserv-ng all automatically for you. Use the IP and Port Number that the appliance prints after it finishes booting (~30 seconds) with the Aircrack tools included instead of a device name.You can set VMware Player to poweroff the appliance when you exit- rather then suspending the appliance (which WILL mess things up). The appliance was built to clean-boot each time, and does not record data to the disk image (it runs off a ramdisk). You can just kill the appliance without running halt or poweroff (it does have a minimal shell). When you reboot it, it will reboot into a clean state each and every time.As usual, I'm not responsible for anything bad. I've tested the appliance with my own RT73 extensively on both my Mac running VMware Fusion, and my handheld OQO running VMware Player. In both cases I'm sure I looked like an idiot with a 6ft USB cable trailing attached to a handheld adapter/antenna/wand walking around with Airodump-NG running, but it worked just fine in both cases nevertheless. I did encounter one quirk with the VMware virtual machine dying, but it took me all of 35 seconds to reboot it to a clean state and I was off again.Let me know if something is broken. I'll try and find time to fix it, and maybe add more support for other USB devices in the future (though I'd probably publish those as their own appliance- to keep the size down, one appliance per USB adapter series/manufacture or something like that).I'd publish the source, but the appliance was built from a Gentoo development environment compiled specifically for this purpose (which is over 600mb in itself) of building embedded images. You can google TinyGentoo, which is what I used to build the appliance, along with many, many other modifications (primarily for Mdev firmware handling issues and a custom INIT script).
saurce: http://tinyshell.be/aircrackng/forum/index.php?topic=2204.0