-
Notifications
You must be signed in to change notification settings - Fork 102
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
Less catching with 8814au #124
Comments
Well, if you are working wireless security/pen testing, I recommend you use a different adapter with a chipset and driver that does a good job. There are no Realtek drivers that do this. Your best bets are the mt7610u, mt7612u and mt7921au chipsets. The Alfa ACHM is very highly rated for this use. It supports monitor mode and |
Thanks for advice, I already ordered AWUS036ACHM. However I found a solution for AWUS1900. I have to make:
I solved it with simple script:
My guess is that some system service is interfering with the adapter. But this script is the easiest solution. |
You might want to try the script I made to help users get into monitor mode: https://github.com/morrownr/Monitor_Mode The primary difference between start-mon.sh and FYI: If you like to work on scripts, start-mon.sh might be a good project for you. There are a lot of improvements that could be made if someone has time. I think having a menu system would be cool. |
And where is the problem? :D |
Hello:) I installed https://github.com/morrownr/8814au/ on rpi4 (Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux )
When I start airodump-ng with AWUS1900 (sudo airodump-ng wlan1) It make much less results (I mean beacons) as TL-WN722N (v1.0).
When I am starting airodump-ng repeatedly TL-WN722N has no problem with that. AWUS1900 show less and less info (low beacons or or no APs (even if there are APs).
Sometimes when I restart rpi4, AWUS1900 make normal result with standard catch of beacons (in the first scan after reboot).
On the pictures is airodump-ng on TL-WN722N and AWUS1900 (in the same time period is different beacons catch). When adapters catching much longer (both adapters working at same time) TL-WN722N catch much more beacons than AWUS1900.
AWUS1900
TL-WN722N
The text was updated successfully, but these errors were encountered: