Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Scanner isn't working | Kali Linux 6.1.0 | Sparrow-wifi 802.11 | Alfa Awus036ACH #87

Open
mkarne1 opened this issue Apr 26, 2023 · 1 comment

Comments

@mkarne1
Copy link

mkarne1 commented Apr 26, 2023

Hi @ghostop14,

I just installed sparrow-wifi on the latest Kali version inside VMWare Fusion. After setting my Alfa Awus036ACH in monitor mode and starting sparrow-wifi, I get no results:

Screenshot 2023-04-26 at 22 12 39

I'm using the latest rtl8812au driver from aircrack-ng. For comparison, here's the scan result of airodump-ng:

CH  1 ][ Elapsed: 24 s ][ 2023-04-26 22:17 

 BSSID              PWR  Beacons    #Data, #/s  CH   MB   ENC CIPHER  AUTH ESSID

 D4:3D:XX:XX:XX:XX  -58        2        0    0 100  866   WPA2 CCMP   PSK  XXXXXXXXX                                                                   
 B4:B0:XX:XX:XX:XX  -56        1        0    0  44  866   WPA3 CCMP   SAE  XXXXXXXXX                                                                   
 2A:BD:XX:XX:XX:XX  -56        1        0    0  36 1733   WPA2 CCMP   PSK  XXXXXXXXX
 DE:F5:XX:XX:XX:XX  -52        1        0    0  36  866   WPA2 CCMP   PSK  XXXXXXXXX
 28:BD:XX:XX:XX:XX  -55        1        0    0  36 1733   WPA2 CCMP   PSK  XXXXXXXXX
 28:BD:XX:XX:XX:XX  -56        1        0    0  36 1733   WPA2 CCMP   PSK  XXXXXXXXX
 D2:F5:XX:XX:XX:XX  -53        1        0    0  36  866   WPA2 CCMP   PSK  XXXXXXXXX
 00:27:XX:XX:XX:XX  -53        1        0    0  36  135   WPA2 CCMP   PSK  XXXXXXXXX
 FA:8F:XX:XX:XX:XX  -63        2        0    0  36  130   OPN              <length:  0>                                                                    
 2A:BD:XX:XX:XX:XX  -54        2        0    0  36 1733   WPA2 CCMP   PSK  XXXXXXXXX
 80:1F:XX:XX:XX:XX -54        3        0    0  11  270   WPA2 CCMP   PSK  XXXXXXXXX
                      

 BSSID              STATION            PWR   Rate    Lost    Frames  Notes  Probes

 48:8F:XX:XX:XX:XX  6A:EC:XX:XX:XX:XX  -58    0 - 6      0        1                                                                                         
 FA:8F:XX:XX:XX:XX  FA:8F:XX:XX:XX:XX   -1    1 - 0      0        3                                                                                         
 C6:F5:XX:XX:XX:XX  38:8B:XX:XX:XX:XX  -45    0 -24    120        7                                                                                         
 00:25:XX:XX:XX:XX7A:4B:XX:XX:XX:XX  -75    0 -12     23       11                                                                                         
 (not associated)   2A:73:XX:XX:XX:XX  -69    0 - 1      2        2                                                                                         
 (not associated)   28:BD:XX:XX:XX:XX  -25    0 - 1      0        1       

Could you help me fixing this issue?

Thanks in advance & best regards!

@cradleinflames
Copy link

cradleinflames commented May 1, 2024

I am having the same issue with Kali 6.6.15 running from a virtual environment. I am using a Netgear AC1200/A6150 wireless adapter (which is not on Kali's approved wireless devices list), as well as having an internal wireless device in the laptop.

Like the OP, I'm unable to see anything using the scan button on the main page but can see devices using airodump-ng.

It should be worth noting, this page WILL update if I go to Falcon->Advanced Scan. Thought that might help identify the issue. Thanks!

UPDATE 1: wlan0 is my internal wifi card, wlan1 is my adapter in monitor mode. When I set the local interface as wlan1 and click scan, it will time out and do nothing. However, if I set it to wlan0 (my internal card), it appears that will result in an update. I'm not sure if that's as intended (and it's a misunderstanding regarding what is meant by "Local Interface" or if this is a bug when two interfaces are connected but only one is in network mode? All the same, I thought I'd mention it.

UPDATE 2: The issue seems to be related to devices already in monitor mode. If a device is not currently in monitor mode, it seems to work fine. When wlan1 was taken out of monitor mode, I could get it to work with the scan command on the main screen. Not sure if the solution is to let the user know not to put it in monitor mode initially or for the software itself to check if it's already in monitor mode?

Also, a "Clear Networks" button that clears the graphs and history would be great as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants