How to install Kali Linux on Virtualbox. Before we begin to install Kali Linux on VirtualBox download Kali Linux and Virtual Box according to your System architecture(64bit or 32bit) and OS(Windows, MAC, or Linux): Latest version of kali Linux → Get it now.
I'm running 4.1.2 in Ubuntu 10.04 host with Gentoo Linux as the guest. I've been trying to use a USB WiFi device (Atheros chipset) in the guest OS, but so far no luck yet. When I put everything in the guest OS in a real machine (i.e.
No guest), the USB WiFi device works OK. If the guest OS is Windows XP, I end up with an yellow exclamation in the Device Manager. If the guest OS is Linux, I'm getting the following kernel message. 3.282211 ath9khtc 1-1:1.0: usbprobeinterface 3.282222 ath9khtc 1-1:1.0: usbprobeinterface - got id 3.772725 usb 1-1: ath9khtc: Transferred FW: ar9271.fw, size: 51312 4.772194 ath9khtc 1-1:1.0: ath9khtc: Target is unresponsive 4.772287 Failed to initialize the device 4.774250 ath9khtc: probe of 1-1:1.0 failed with error -22 4.775452 usbcore: registered new interface driver ath9khtc # lsusb grep -i ath Bus 001 Device 003: ID 0cf3:9271 Atheros Communications, Inc.
AR9271 802.11n My guess is that the USB WiFi device itself and the setup in the Linux guest might not be an issue, because when I use a real machine, everything works perfectly. Confirmed this issue using Windows 7 x64 host with Debian Squeeze (backports linux-image-686 3.2 and backports firmware-atheros 0.35). Virtualbox version is 4.1.8 Device: TP-Link WN821N v3 (using Atheros AR7010+AR9287) Tested the device on Debian without using virtualbox, and it works fine. Same issue using Virtualbox 4.1.10 with Host system Windows 7 x64 Ultimate and guest system Backtrack 5. Using TP-Link TL-WN722N USB adapter.
USB adapter works fine in Backtrack 5 when booted up from a USB stick but not in a virtual machine. Has same issue in Mint 12 x64. Any fix on the way?
50.397906 usb 1-2: ath9khtc: Transferred FW: ar9271.fw, size: 51312 51.390246 ath9khtc 1-2:1.0: ath9khtc: Target is unresponsive 51.390251 Failed to initialize the device 51.401861 ath9khtc: probe of 1-2:1.0 failed with error -22 51.401876 usbcore: registered new interface driver ath9khtc. I can confirm this same behaviour on vmware. Had spent hours in trying to figure it out on both virtualbox and vmware. However, there is a workaround in vmware. Using auto-connect feature, physically extract the device from the usb slot of the host machine and re-insert it back, and it magically works. Every single time.
If you disconnect the device via the menu, it behaves exactly like above (target is unresponsive, etc) in and Vmware guests alike. Confirmed it on two different guest distro's (gentoo and mint) with a mint 12 host. Hope this helps. Same issue using Virtual Box 4.2.4 on Ubuntu 10.10 host. Trying to make my netgear n150 working on Backtrack guest.
Oracle / Virtual Box Developers, I have been following this ticket for a while now. I always update Virtual Box to the latest patches. I am now at 4.2.10.
I am also experiencing the same USB errors. My setup is as follows: HOST OS is Windows 7 64bit Ultimate Guest OS's are Linux Mint 14 Mate and Ubuntu 12.04 LTS I get the same error messages in syslog from both Guest OS's. See Below: ath9khtc 1-2:1.0: ath9khtc: Target is unresponsive ath9khtc: Failed to initialize the device usb 1-2: ath9khtc: USB layer deinitialized I have a TL-WN722N USB WiFi Adapter that I am trying to use. This is a known compatible card with both Linux versions listed above.
I have tested it with Linux installed directly on physical hardware and it works perfectly. Just not in the Virtual Machine. Oracle, Please look into this and provide an update as soon as possible. Replying to: The preferred way to get Internet over wlan into a VM is to use the WLAN adapter on the host and using normal NAT for the VM. Passing USB WLAN adapters to the guest is almost untested. I too require this feature.
My VBox host is Solaris. I need to pass-through my TP-LinK Wireless N USB Adapter TL-WN722N to a Linux VM to create a Wireless Access Point. I have been waiting for a fix for a long time and still hope for a resolution soon so I can retire my old and slow current Wireless AP hardware. Hello Oracle Team, Firstly I'd like to say that I'm very appreciative of and all the work you guys have put into this awesome piece of free software over the past years. Although I've seen a steady flow of great improvements, there are some issues, such as the one listed in this ticket, which have been open for a while. As I'm sure you're aware by know, there are many good and robust wifi dongles/cards which are utilizing AR9271 Atheros chipset, but most of them unfortunately don't have native Mac Os X support, which is why people like me have to rely your USB pass-through support. In my case, the guest system is Debian, which gives me a 'Target is unresponsive' error.
Atheros have recently published open firmware for this chipset , so I was wondering if you might consider trying to fix this issue in one of your next releases? If so, it'd be great if we could get an ETA on it? Regards, Zarko. Same issue with VB 4.3.0 Beta2. Host win7 ultimate, guest: Kali-Linux.
Sad but true. Sorry to state the obvious - but we don't have the necessary hardware. I only see complaints, and no one offers any kind of help. Remember, you're taking the free ride so it's stretching things to expect that we can justify investing time and money into something which for some funny reason no customer has ever mentioned. We do what's possible, but as long as we don't have the hardware we have to rely on the community. Bugs don't fix themselves magically if many people in a bug ticket say that they're affected, too.
I know that it's cheap gear, but in a big corporation every cent needs to be justified, which is only easily done if there's a customer with a support contract anywhere in sight. Replying to: Making VirtualBox shareware, just for some USB WiFi adapter support which as Frank stated above should be handled by the host OS? I can't even imagine what the reaction from the open source community would be. Don't think this gets us closer to a solution.
Dear Klaus, I am having difficulty to understand your position. All these users are talking about some problem about the way handles the USB allocation to guests. But it somehow comes down to whether the resource allocation for finding a solution is justifiable or not. This is not just a problem limited to the Atheros USB Driver.
When it comes to making USB hardware available to guests, it is always a gamble whether it would work or not. There are many loopholes USB Capture for guests.
I myself having the same issue exactly as described by many people above. Also I have returned another USB Wi-Fi adapter which was not even posible to attach to guest except for only some occassions. I can use the same Atheros hardware without any problem with VMWare Workstation or when I boot my system directly with BTR/Kali/Ubuntu. So shall we continue on having this discussion whether it is worth to fix the problem or get down to scrutinize the USB capture code? This is the real question. You say nobody gives you a hand what is that you need to start on working over the USB Capture issue?
Reading complaints like it's shocking to see a bug reports started 2 years ago and the virtualbox still unable to fix this bug until now doesn't improve our willingness to invest time. And as we mentioned several times in other tickets: We have to prioritize our work as we have limited resources. Even if a bug is open for several years it does not mean that the priority of such a bug increases. You might be aware that there are about 4,000 tickets open in the public bug tracker.
And of course, every reporter thinks that his issue is the most important one. Sorry to say, but we have a different view. Replying to: Reading complaints like it's shocking to see a bug reports started 2 years ago and the virtualbox still unable to fix this bug until now doesn't improve our willingness to invest time. And as we mentioned several times in other tickets: We have to prioritize our work as we have limited resources. Even if a bug is open for several years it does not mean that the priority of such a bug increases. You might be aware that there are about 4,000 tickets open in the public bug tracker.
And of course, every reporter thinks that his issue is the most important one. Sorry to say, but we have a different view. OK Thank you for the information. Trying to attach USB devices to a Virtual system is a low priority issue with almost no interest to anyone. Keremer, you're misinterpreting our replies.
It is NOT low priority to have working USB passthrough, but in this particular case there are two prerequisites for making progress, and that's what's causing the complete stand still:. Having an affected device (we don't care if it's ath9k or not). Having free developer resources At the moment condition 1 isn't met (we have no USB devices available which can be made working), this won't make progress. If the USB passthrough code would have trouble with a wide variety of devices then I'd agree that starting the investigation from the source code side is a good approach, but this isn't the case. The vast majority of devices does work very well, just extremely few don't, and then staring at the sources is a waste of time.
We'd have USB debugging tools available, but without an affected device they don't help. I think I repeated 'affected device' by now enough to make it obvious that this is the key to make progress, and in my previous message I already mentioned that even getting such cheap device needs a lot of effort, which won't happen if everyone is busy and budgets are tight. That's what Frank summarized in a somewhat frustrated way as 'prioritize work'. As all my previous subtle hints were only abused as starting points for complete misinterpretations of the situation I'll spell it out now: if we miraculously find such a device (which is working in general) in our mail then condition 1 will be out of the way, and while that doesn't guarantee immediate developer availability (can still take months) it's resolving the so far blocking prerequisite. We promise to send it back if the owner wants that, and in any case this will be acknowledged in the documentation as a contribution if desired.
Replying to: keremer, you're misinterpreting our replies. It is NOT low priority to have working USB passthrough, but in this particular case there are two prerequisites for making progress, and that's what's causing the complete stand still:. Having an affected device (we don't care if it's ath9k or not). Having free developer resources This is what I am trying to tell. I don't know.any.
USB Wi-Fi adapter that works with your USB passthrough. Currently I have tested 3 different adapters with different chipsets. To get them workign was always hectic.
Sometimes it worked to boot the system and then attaching the adapter (BCM, ATH and RealTek) solved the issue temporarily until you remove/attach and sometimes did not. Sometimes could isolate the adapter successfully from the hypervisor and attach it to the virtual gust. Sometimes it did not. In fact it seems that there's a problem with USB passthrough not only a single chipset. Please use whatever USB Wireless adapter at your hand and see if it is removed from the system and attached to the guest every time you plug it in and out. At the moment condition 1 isn't met (we have no USB devices available which can be made working), this won't make progress. If the USB passthrough code would have trouble with a wide variety of devices then I'd agree that starting the investigation from the source code side is a good approach, but this isn't the case.
The vast majority of devices does work very well, just extremely few don't, and then staring at the sources is a waste of time. We'd have USB debugging tools available, but without an affected device they don't help. I think I repeated 'affected device' by now enough to make it obvious that this is the key to make progress, and in my previous message I already mentioned that even getting such cheap device needs a lot of effort, which won't happen if everyone is busy and budgets are tight.
That's what Frank summarized in a somewhat frustrated way as 'prioritize work'. As all my previous subtle hints were only abused as starting points for complete misinterpretations of the situation I'll spell it out now: if we miraculously find such a device (which is working in general) in our mail then condition 1 will be out of the way, and while that doesn't guarantee immediate developer availability (can still take months) it's resolving the so far blocking prerequisite. We promise to send it back if the owner wants that, and in any case this will be acknowledged in the documentation as a contribution if desired. I guess you don't need a miracle to correct this situation because it is about USB passthrough and not specific devices. Besides if you please indicate the correct channels I am sure someone could donate an adapter for you. If it were only a single chip issue there were not so many complaints about USB Passtrhrough in this or different treads. It is the real miracle how could you evade this for such a long time though.
In fact nobody expects immediate developer dispatch but there has been several major releases during the last two years and there was no improvement in USB passthrough about the attachment of any wireless USB devices. Hi, I am currently experiencing this bug and am willing to put some time in to help get it fixed. Please let me know how I can help. Here are the circumstances in which I have experienced this issue:.
Virtualbox Version: 4.3.6, 4.1.12 (ubuntu repos). USB Extension Pack: Installed. Host OS: Ubuntu 12.04 64-bit and Debian 7.0 Wheezy 64-bit.
Host Kernel: Default Ubuntu (3.5.0-45) and Wheezy kernels. Guest: Kali Linux 32-bit. Guest Kernel: 3.12-pae, 3.7-pae. Guest Additions: Installed Device is an Alfa AWUS036NHA, chipset AR9271. I've also been bitten by this bug. Running latest Ubuntu 13.10 stable in latest stable virtualbox (4.3.6) with latest stable virtualbox matching extensions (also 4.3.6) with latest stable vagrant setting the whole thing up.
Using standard off the shelf atheros ath9k-based usb wifi. Got a workaround for me: Hypervisor: Ubuntu Desktop 14.04: 4.3.18 VirtualGuesAdditions: yes Guests: Ubuntu 12.04, Ubuntu 14.04 Wifi Dongle: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 Atheros AR9271 Driver: ath9khtc.
Get Vendor & Product ID from wifi dongle ( with lsusb). check if the module ath9khtc on your hypervisor is loaded. if yes, unload module ( modprobe -r ath9khtc). create a blacklist file in /etc/modprobe.d/ for the module: vim /etc/modprobe.d/blacklist-ath9k.conf type in the new file: blacklist ath9khtc save file. repluge the wifi dongle.
create manualy for your VM guest a USB filter ( settings - usb - usb connector with blue circle) and add the Vendor & Product ID. start your VM. with dmesg grep htc you shoud get: 2.981893 usb 1-1: ath9khtc: Firmware htc9271.fw requested 2.982436 usbcore: registered new interface driver ath9khtc 3.329829 usb 1-1: ath9khtc: Transferred FW: htc9271.fw, size: 51272 3.580004 ath9khtc 1-1:1.0: ath9khtc: HTC initialized with 33 credits 4.263725 ath9khtc 1-1:1.0: ath9khtc: FW Version: 1.3 Thats it! I hope I could help.
Hi I have a VBOX 4.3.28 in a debian jessie host. Im trying to use this TP-LINK TL-WN722N in a Kali linux vm, I follow the steps above, but I don't have any positive results, below I post the exit of the commands. Replying to: keremer, you're misinterpreting our replies.
It is NOT low priority to have working USB passthrough, but in this particular case there are two prerequisites for making progress, and that's what's causing the complete stand still:. Having an affected device (we don't care if it's ath9k or not). Having free developer resources At the moment condition 1 isn't met (we have no USB devices available which can be made working), this won't make progress.
If the USB passthrough code would have trouble with a wide variety of devices then I'd agree that starting the investigation from the source code side is a good approach, but this isn't the case. The vast majority of devices does work very well, just extremely few don't, and then staring at the sources is a waste of time. Is this still an issue? I'd really like to have USB passthrough work properly. If you post the mailing address with Attn To: line so it gets to the right place I will have an atheros wifi dongle in the mail to you tomorrow. Replying to: Hi I have a VBOX 4.3.28 in a debian jessie host. Im trying to use this TP-LINK TL-WN722N in a Kali linux vm, I follow the steps above, but I don't have any positive results, below I post the exit of the commands.
Issue is still present in 5.0.8. Fix proposed by SamuelRR does not works for Debian 7.2 (wheezy) with backported firmware, and Netgear N150: target is still unresponsive: 77 usb 1-1: firmware: agent loaded htc9271.fw into memory 08 usb 1-1: ath9khtc: Transferred FW: htc9271.fw, size: 50980 40 ath9khtc 1-1:1.0: ath9khtc: Target is unresponsive 05 ath9khtc: probe of 1-1:1.0 failed with error -22 15 usbcore: registered new interface driver ath9khtc (50980- size of new firmware). The AR9271 works with newer Linux guest kernels, starting around 3.13 or so. It indeed fails with older Linux kernels when using EHCI emulation due to a bug.
The AR9271 also fails with older Linux guest kernels when using xHCI emulation. Again newer guest kernels work starting around 3.5.
This can't be fixed in. The ath9khtc driver is poorly written and schedules bulk transfers on interrupt endpoints. That causes both the EHCI and xHCI problems. The EHCI one we should be able to work around, the xHCI one not so. There are separate problems with Windows guests.
Following recommended USB Wireless cards appears to be working for Kali Linux (i.e. Monitor, injection etc.).Note. These are not in any type of order.Note. A common problem in pentest distro such as Kali or BackTrack Linux is when users trying to use a card which is not supported or there just isn’t a supported driver. Most of the following cards are priced below $50USD and they take care of a massive headache and saves time to troubleshoot driver issues rather than investing time to actually do something. With each update these makeshift fixes seems to break old drivers and you end up doing the whole thing again and again.
A good card will allow you to crack Wifi on the fly or at least make it easier. Some examples are:. This whole drama goes away when you get one of the recommended usb wireless cards. Then again, I got few different Wifi cards and I managed to make all of them work with Kali Linux including injection and monitor mode etc. It really depends on the user and type of card. This guide will possibly help someone who just got an unsupported card and/or tired of wasting time troubleshooting existing card and would rather spend some $$ to have this problem go away once and for all.
This post is again adapted from none other than post in. POST UPDATED: – Added Linksys WUSB54GC v1 Compact Wireless-G USB Adapter to recommended list. – Added Alfa RangeBooster Antenna’s and classic AWUS036H adapters (1000mW and 2000mW) to recommended list. See List of Nethunter supported devices. – Added a poll. Please vote (you don’t need to register) so that readers can find the best card quickly. poll id=”2″ 2.4GHz Adapters Rokland N3.
Ralink RT3070. 700 mW. Detachable antenna (RP-SMA). IEEE 802.11b/g/n. 150Mbps. WEP, WPA/WPA2, WPS.
USB 2.0 Alfa AWUS036NHA. Atheros AR9271.
800 mW (29dBm). Detachable antenna (RP-SMA).
IEEE 802.11b/g/n. 150Mbps. WEP, WPA/WPA2, WPS. USB 2.0 Alfa AWUS036H High power 1000mW 1W 802.11b/g and Alfa AWUS036NH 2000mW 2W 802.11g/n. Atheros AR9271.
800 mW (29dBm). Detachable antenna (RP-SMA). IEEE 802.11b/g/n.
150Mbps. WEP, WPA/WPA2, WPS.
USB 2.0 TP-Link WN722N. Atheros AR9002U. 500 mW?.
Detachable antenna (RP-SMA). IEEE 802.11b/g/n. 150Mbps. WEP, WPA/WPA2, WPS. USB 2.0 Linksys WUSB54GC v1. Chipset: Ralink 2573 USB. Driver: rt73usb.
IEEE 802.11b/g. 150Mbps. WEP, WPA/WPA2, WPS. USB 2.0. Stack: mac80211.
Injection: Yes. See discussion: 5GHz (& 2.4GHz) Adapters Rosewill RNX-N600UBE. Ralink RT3572. 100 mW?. Detachable antenna (SMA).
IEEE 802.11a/b/g/n. 300Mbps. WEP, WPA/WPA2, WPS. USB 2.0 Update: I should add that the Rosewill RNX-N600UBEs they’re selling at Amazon come with Ralink 5572s now so someone looking for a plug-and-play option will be disappointed, and frustrated, and praying that someone will see this comment on a half-year old article and give them a little help.
Comment:So unless someone else can verify that Ralink RT3572 was replaced by Ralink 5572, I am marking Rosewill RNX-N600UBE incompatible. Thanks, for the post.
I am trying to hack my own 802.11n Belkin Router or My old Belking 54g running dd-wrt to see if I can get the passwords I made up and have them locked down with. I am using a Toshiba Satellite with Kali Linux Live 32bit Disk. I will let you know how it goes once I get going. To Start I was wodering if the wifi card in the toshiba was compatible with Kali Linux but I now know it is because i see all the networks around us.
![Install Wireless Driver On Kali Linux Virtualbox Windows Install Wireless Driver On Kali Linux Virtualbox Windows](/uploads/1/2/5/4/125441107/490869983.jpg)
I guess it uses an intel card for wifi but i may have to look it up to get exact model # I am a wedding photographer and use a lot of band width on my uploads. My websites: link removed (Portfolio) link removed (Free Wedding Websites, Services, Help, Forum, Q&A link removed (Classified Ads Never Expire Unless Deleted). Thank you so much, UUI. I struggled with this for many days (almost to the point of suicide), but then read your helpful comment and (as if by magic), had success! It really works!
I’m so eager to show other people my discovery, but I must give you the credit. At some point or another, we’ve all been there. How much time and wasted effort could be saved if more caring and insightful people (like yourself) would just take the briefest moment to extend a hand to others as you have done.
I also want to praise your honesty. Too often, the commenter seeks under-handed ways of trying to impress their peers. You, otoh, simply “tell it like it is” without the usual politics and divisive remarks totally refreshing! I do have one clarification, though; what happens if you change your position? What I mean is, “What if I eat the other side?” Do you know if that will still work?
Hi blackMORE Ops, I am trying to get into this world and your website is the most clear Ive found. I have one question (here, I have thousands of questions): Eventhough you said there isnt a better card, I guess thee should be differences between them, specially about range issues. The alfa one looks to have 800mW, so makes that the most powerful one speaking about range? Some friends recommended me to get directional antennas instead of omnidirectional ones, but as far as I know, I can plug those directional antennas into the alfa one to increase its range right? Thanks in advance and go on with this awesome website! Hi Unkim, Thank you. Amazon got bunch of Directional Antennas which looks promising.
In my mind, Directional Antenna’s would be best as you can pin point and isolate signals. But if you can get a powerful enough omnidirectional antenna, then I guess it doesn’t matter anymore. At the end, it comes down to how good the hardware is and how subtle the signal is. I’ll add a link soon when I have some spare time. I’ve read about people who got Rapsberry Pi setup with Omnidirectional antenna and drive around the neighborhood to capture handshake packets. Don’t know if those stories are true or just hoaxes, (or legal in most countries?) but you can understand it is certainly a possibility.
Thanks again for your comment and kind words. I try my best.
Feel free to register and post your own articles if you feel like. Today I ordered from Amazon Alfa AWUS036NHA for $38.
I am completely new to Linux. I saw 6 awesome books on Amazon for beginners (i.e. Linux Bible) to teach me all the commands and other important things. I can’t wait to get the books and start reading! I have never penetrated a network before so I am excited to do it for the first time.
![Wireless Wireless](http://enekumvenamorublog.files.wordpress.com/2014/09/windows-install06.png)
My only worry is about wordlists. I just don’t understand how the #$%@ a wordlist can have my password in it. For example, my real password for my home network has this combination, “3 letters + 7 digits + 1 capital letter + 4 letters”. I know an incredible password should be 35 characters long and should have a combination of everything, especially special characters, so I will change it to that soon! Anyway, my current passphrase iis completely unique and no one on Earth could think of this password.
How the @#$% can a wordlist have my password if I’m the only human on Earth who could have thought of it? Someone please explain this to me:(. Will I waste countless hours trying to crack my own password and for nothing?
Did I just waste $38? My e-mail: I’m new to linux so any tips or info will be greatly appreciated it, especially about wordlists to download!.
I have ordered 10+ TP-Link WN722N wifi adapters over the last 3 months and ALL are BRAND NEW in the sealed box which ALL of them are “v1.0″.