darlord, Thanks for your reply, i have followed the tutorial which S3M73X advised but didn't work for me.Quote:
Originally Posted by darlord
can you please advise the way you succeed as step by step if possible, thanks in advance.
Printable View
darlord, Thanks for your reply, i have followed the tutorial which S3M73X advised but didn't work for me.Quote:
Originally Posted by darlord
can you please advise the way you succeed as step by step if possible, thanks in advance.
Hi guys!
I'm new to BT :)
I'm really struggling with it. I followed the guide and everything appears to work, but when I do airodump-ng mon0 it doesn't find anything. I've left it for 10 or more mins, and it's still not found anything. Surely it should be quicker than that?Quote:
Originally Posted by darlord
A few questions for you though:
1 - Following the guide, I can't get it to update unless I remove "linux-headers-$(uname -r)" from the line. Tried getting rid of "-$(uname -r)", but it still says "Linux Headers not found". Does this matter that it's not updated the linux-headers?
2 - Am I right in thinking I follow the guide for the ALFA-AWUS050NH and use the RT2800usb drivers?
3 - Do I stop at "modprobe rt2800usb" or is there anything else I need to do?
I've tried this in BT4-Final VM and native via USB on my laptop. I'm pretty sure the 'card' is working, cos I can use it fine in Windows.
Any help on getting this stupid thing working would be greatly appreciated :)
Make sure you follow the HOWTO on hard drive install and or VM install. I hoped it went without saying this can't be done on the dvd, you have to have it installed into a persistent environment. The VM howto describes how to update the linux headers.
@P0k3_P1e - do aand you should seeCode:modprobe rt2800usb
iwconfig
thenCode:root@bt:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
When you see the "monitor mode enabled on mon0" then you're all good.Code:root@bt:~# airmon-ng start wlan0
Interface Chipset Driver
wlan0 Unknown rt2800usb - [phy0]
(monitor mode enabled on mon0)
@login63 -
can you see any APs with airodump-ng?
after following the tutorial i can see the "monitor mode enabled on mon0" message but can't find any AP with airodump-ng mon0
darlord thnanks for the reply, but there is no any new info to help to solve the matter. I installed all again with the allmost the same result. The drivers rt2800usb are loaded but after airmon-ng start wlan0 the mon0 is appearing after 40 seconds and in airodump-ng the chanels are changing very slowly. It shows some time nothing , some time (after new restart) only few stations ( only 3-4, in WinXP there are 62) and only in one chanel - 3 or 9. There is something wrong but I can not find what?
I have the same issue. No AP's shows up after airodump-ng mon0. Been googling for weeks trying to solve this issue.
yeah I have the same problem, card enabled and airmon ok, but then it always finds 0 AP if I run e.g. aireplay-ng --test.
Any idea?
Sorry guys, I'm out of ideas. Mine finds about 20 APs when I'm sitting here and my MacBook finds 5, so my ALPHA is way more sensitive than the card in my MacBook.
Are you saying that when you use the ALPHA under Windows it finds APs, but not with BT? Or was it a different card?
The problem is driver rt2800usb - still not well suited for AWUS036NH. The card is strating in monior mode but in fact it is working only in one channel (mostly 3 or 9, or other with no rule which one). On this channel it is able to inject and to crack but you can not chanhge actually to other.So we have to wait for new stable driver for RT3070.
Is your card channel hopping, or is set to one channel? Perhaps there is no networks on the channel your scanning. try running from a fresh boot, before you have tried to connect to any networks, or used wicdQuote:
Originally Posted by astabada