How to get Alfa awus036nha to work with Kali Linux?
Im running Kali linux 64bit 1.07 as a guest os through virtualbox 4.3.12 r93733. Ive also installed the VirtualBox 4.3.12 Oracle VM VirtualBox Extension Pack. I have bridged my hosts network connection (Intel(R) Wireless-N 7260) with Kali and I have set up the Alfa 036nha as a usb device for kali through virtualbox.
iwconfig in kali gives no wireless extensions.
ifconfig shows my bridged connection and Local loopback.
lsusb shows:
Bus 001...... Atheros Communications, inc. AR9271 802.11n
I thought that maybe it didnt have the right drivers so i tried to apt-get install firmware-atheros but it said that it was already installed.
I really dont know what I should do here.. anyone care to help me out?
You should now that Im not too good with Linux etc.
Edit:
I found this https://www.youtube.com/watch?v=K1ETBeRQBs4
Which helped me getting the Alfa card to work in Kali. The trick was to add a new custom USB device in virtualbox where you just take the vendor ID and product ID from the alfa device and leave the other boxes blank.
So now when i run ifconfig i get that wlan0 is up (Alfa) but eth0 is down (Intel(R) Wireless-N 7260).
Now however the problem is that when I plug in the Alfa device my network connection from my other wifi ceases to work (Intel(R) Wireless-N 7260) (the connection bridged from my host). It disconnects in the host aswell. If I connect to a wifi (with 7260) in the host with kali and alfa running the alfa stops working in kali... I want to have them both running.
Anyone knows how to fix that?
linux networking wireless-networking virtualbox
add a comment |
Im running Kali linux 64bit 1.07 as a guest os through virtualbox 4.3.12 r93733. Ive also installed the VirtualBox 4.3.12 Oracle VM VirtualBox Extension Pack. I have bridged my hosts network connection (Intel(R) Wireless-N 7260) with Kali and I have set up the Alfa 036nha as a usb device for kali through virtualbox.
iwconfig in kali gives no wireless extensions.
ifconfig shows my bridged connection and Local loopback.
lsusb shows:
Bus 001...... Atheros Communications, inc. AR9271 802.11n
I thought that maybe it didnt have the right drivers so i tried to apt-get install firmware-atheros but it said that it was already installed.
I really dont know what I should do here.. anyone care to help me out?
You should now that Im not too good with Linux etc.
Edit:
I found this https://www.youtube.com/watch?v=K1ETBeRQBs4
Which helped me getting the Alfa card to work in Kali. The trick was to add a new custom USB device in virtualbox where you just take the vendor ID and product ID from the alfa device and leave the other boxes blank.
So now when i run ifconfig i get that wlan0 is up (Alfa) but eth0 is down (Intel(R) Wireless-N 7260).
Now however the problem is that when I plug in the Alfa device my network connection from my other wifi ceases to work (Intel(R) Wireless-N 7260) (the connection bridged from my host). It disconnects in the host aswell. If I connect to a wifi (with 7260) in the host with kali and alfa running the alfa stops working in kali... I want to have them both running.
Anyone knows how to fix that?
linux networking wireless-networking virtualbox
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29
add a comment |
Im running Kali linux 64bit 1.07 as a guest os through virtualbox 4.3.12 r93733. Ive also installed the VirtualBox 4.3.12 Oracle VM VirtualBox Extension Pack. I have bridged my hosts network connection (Intel(R) Wireless-N 7260) with Kali and I have set up the Alfa 036nha as a usb device for kali through virtualbox.
iwconfig in kali gives no wireless extensions.
ifconfig shows my bridged connection and Local loopback.
lsusb shows:
Bus 001...... Atheros Communications, inc. AR9271 802.11n
I thought that maybe it didnt have the right drivers so i tried to apt-get install firmware-atheros but it said that it was already installed.
I really dont know what I should do here.. anyone care to help me out?
You should now that Im not too good with Linux etc.
Edit:
I found this https://www.youtube.com/watch?v=K1ETBeRQBs4
Which helped me getting the Alfa card to work in Kali. The trick was to add a new custom USB device in virtualbox where you just take the vendor ID and product ID from the alfa device and leave the other boxes blank.
So now when i run ifconfig i get that wlan0 is up (Alfa) but eth0 is down (Intel(R) Wireless-N 7260).
Now however the problem is that when I plug in the Alfa device my network connection from my other wifi ceases to work (Intel(R) Wireless-N 7260) (the connection bridged from my host). It disconnects in the host aswell. If I connect to a wifi (with 7260) in the host with kali and alfa running the alfa stops working in kali... I want to have them both running.
Anyone knows how to fix that?
linux networking wireless-networking virtualbox
Im running Kali linux 64bit 1.07 as a guest os through virtualbox 4.3.12 r93733. Ive also installed the VirtualBox 4.3.12 Oracle VM VirtualBox Extension Pack. I have bridged my hosts network connection (Intel(R) Wireless-N 7260) with Kali and I have set up the Alfa 036nha as a usb device for kali through virtualbox.
iwconfig in kali gives no wireless extensions.
ifconfig shows my bridged connection and Local loopback.
lsusb shows:
Bus 001...... Atheros Communications, inc. AR9271 802.11n
I thought that maybe it didnt have the right drivers so i tried to apt-get install firmware-atheros but it said that it was already installed.
I really dont know what I should do here.. anyone care to help me out?
You should now that Im not too good with Linux etc.
Edit:
I found this https://www.youtube.com/watch?v=K1ETBeRQBs4
Which helped me getting the Alfa card to work in Kali. The trick was to add a new custom USB device in virtualbox where you just take the vendor ID and product ID from the alfa device and leave the other boxes blank.
So now when i run ifconfig i get that wlan0 is up (Alfa) but eth0 is down (Intel(R) Wireless-N 7260).
Now however the problem is that when I plug in the Alfa device my network connection from my other wifi ceases to work (Intel(R) Wireless-N 7260) (the connection bridged from my host). It disconnects in the host aswell. If I connect to a wifi (with 7260) in the host with kali and alfa running the alfa stops working in kali... I want to have them both running.
Anyone knows how to fix that?
linux networking wireless-networking virtualbox
linux networking wireless-networking virtualbox
edited Jul 11 '14 at 12:59
grateful_n00bz0r
asked Jul 10 '14 at 18:25
grateful_n00bz0rgrateful_n00bz0r
21113
21113
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29
add a comment |
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29
add a comment |
6 Answers
6
active
oldest
votes
Buy powered usb hub + Y cable, run adapter through thst
Usually problem is electricity with usb can't provide enough for adapter.
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
add a comment |
I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.

add a comment |
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.
The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
add a comment |
This answer fixed this issue exactly as described above.
apt-get install firmware-atheros
Try to uninstall and reinstall the firmware if it already exists:
apt-get remove firmware-atheros
apt-get install firmware-atheros
add a comment |
If anyone followed the video the OP posted, got wlan0 showing up in ifconfig but are stuck with the virtual box USB indicator blinking red
From Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select
"enable network adapter" and the "not attached" option then run
virtual box with kali linux, then after kali loads connect the network
adapter, and let it load. After half a minute go to Devices -> usb
devices -> and select your adapter
Then it should load.
add a comment |
Running Kali 2019.1, on VirtualBox.
do sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f781514%2fhow-to-get-alfa-awus036nha-to-work-with-kali-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
Buy powered usb hub + Y cable, run adapter through thst
Usually problem is electricity with usb can't provide enough for adapter.
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
add a comment |
Buy powered usb hub + Y cable, run adapter through thst
Usually problem is electricity with usb can't provide enough for adapter.
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
add a comment |
Buy powered usb hub + Y cable, run adapter through thst
Usually problem is electricity with usb can't provide enough for adapter.
Buy powered usb hub + Y cable, run adapter through thst
Usually problem is electricity with usb can't provide enough for adapter.
answered Jul 17 '15 at 5:44
BotmasterBotmaster
15019
15019
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
add a comment |
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
1
1
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
OP already answered his question so this answer is not needed.
– Davidenko
Jul 17 '15 at 5:52
3
3
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
The answer can be useful for other users who have similar issue and possibility that youtube file couldn't help them. It was my experience which helped me to fix the issue, I like to share it with others as it would be helpful, if not helpful definitely not harmful as well!
– Botmaster
Jul 17 '15 at 6:17
add a comment |
I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.

add a comment |
I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.

add a comment |
I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.

I tried everything on this post without success, the blinking green icon on the USB controller wasn't happening for me.
So after researching for some hours, and trying several ways to troubleshoot the issue, the answer for me was to set the USB 3.0 (xHCI) Controller under USB settings on virtual box, I believe this feature is available on Virtual box 5.0.16 and up.

edited Mar 24 '16 at 13:51
bummi
1,48131422
1,48131422
answered Mar 24 '16 at 12:04
Jaime PoloJaime Polo
111
111
add a comment |
add a comment |
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.
The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
add a comment |
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.
The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
add a comment |
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.
The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
This somehow solved my problem https://www.youtube.com/watch?v=K1ETBeRQBs4.
The additional problem I talked about only seems to be present sometimes and most of the times both wlan interfaces work.
answered Jul 12 '14 at 16:51
grateful_n00bz0rgrateful_n00bz0r
21113
21113
add a comment |
add a comment |
This answer fixed this issue exactly as described above.
apt-get install firmware-atheros
Try to uninstall and reinstall the firmware if it already exists:
apt-get remove firmware-atheros
apt-get install firmware-atheros
add a comment |
This answer fixed this issue exactly as described above.
apt-get install firmware-atheros
Try to uninstall and reinstall the firmware if it already exists:
apt-get remove firmware-atheros
apt-get install firmware-atheros
add a comment |
This answer fixed this issue exactly as described above.
apt-get install firmware-atheros
Try to uninstall and reinstall the firmware if it already exists:
apt-get remove firmware-atheros
apt-get install firmware-atheros
This answer fixed this issue exactly as described above.
apt-get install firmware-atheros
Try to uninstall and reinstall the firmware if it already exists:
apt-get remove firmware-atheros
apt-get install firmware-atheros
edited Nov 7 '14 at 2:17
Kevin Panko
5,939113648
5,939113648
answered Nov 6 '14 at 21:35
NetsecNetsec
1
1
add a comment |
add a comment |
If anyone followed the video the OP posted, got wlan0 showing up in ifconfig but are stuck with the virtual box USB indicator blinking red
From Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select
"enable network adapter" and the "not attached" option then run
virtual box with kali linux, then after kali loads connect the network
adapter, and let it load. After half a minute go to Devices -> usb
devices -> and select your adapter
Then it should load.
add a comment |
If anyone followed the video the OP posted, got wlan0 showing up in ifconfig but are stuck with the virtual box USB indicator blinking red
From Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select
"enable network adapter" and the "not attached" option then run
virtual box with kali linux, then after kali loads connect the network
adapter, and let it load. After half a minute go to Devices -> usb
devices -> and select your adapter
Then it should load.
add a comment |
If anyone followed the video the OP posted, got wlan0 showing up in ifconfig but are stuck with the virtual box USB indicator blinking red
From Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select
"enable network adapter" and the "not attached" option then run
virtual box with kali linux, then after kali loads connect the network
adapter, and let it load. After half a minute go to Devices -> usb
devices -> and select your adapter
Then it should load.
If anyone followed the video the OP posted, got wlan0 showing up in ifconfig but are stuck with the virtual box USB indicator blinking red
From Youtube user Stas Sorokin posted in the Youtube comments of the video mentioned by the OP:
The trick is to go to your kali settings in VB go to network, select
"enable network adapter" and the "not attached" option then run
virtual box with kali linux, then after kali loads connect the network
adapter, and let it load. After half a minute go to Devices -> usb
devices -> and select your adapter
Then it should load.
answered Oct 31 '15 at 16:56
CynapseCynapse
11616
11616
add a comment |
add a comment |
Running Kali 2019.1, on VirtualBox.
do sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
add a comment |
Running Kali 2019.1, on VirtualBox.
do sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
add a comment |
Running Kali 2019.1, on VirtualBox.
do sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
Running Kali 2019.1, on VirtualBox.
do sudo apt update; sudo apt install realtek-rtl88xxau-dkms;
Once I did that, I heard my Alfa disconnect and reconnect from Windows, and all of a sudden, I had wlan0 interface. No reboot needed.
source:https://www.kali.org/releases/kali-linux-20171-release/
answered Feb 28 at 13:28
AriAri
29118
29118
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f781514%2fhow-to-get-alfa-awus036nha-to-work-with-kali-linux%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If there are any suggestions about using the AWUS036NH that'd be great since I'm having this same issue but with the Ralink chipset.
– slow_excellence
Jul 10 '14 at 19:43
I'm really surprised by the number of answers that this question got.
– Don't Root here plz...
Oct 28 '16 at 14:29