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

Less catching with 8814au #124

Open
VeritasLibera opened this issue Jan 31, 2024 · 4 comments
Open

Less catching with 8814au #124

VeritasLibera opened this issue Jan 31, 2024 · 4 comments

Comments

@VeritasLibera
Copy link

VeritasLibera commented Jan 31, 2024

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
01

TL-WN722N
02

@morrownr
Copy link
Owner

Hi @VeritasLibera

When I start airodump-ng with AWUS1900...

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 active monitor mode. I can recommend others but you can go to the site Main Menu and read menu items 1 and 2 which should provide a lot of information:

https://github.com/morrownr/USB-WiFi

@morrownr

@VeritasLibera
Copy link
Author

VeritasLibera commented Feb 1, 2024

Thanks for advice, I already ordered AWUS036ACHM. However I found a solution for AWUS1900. I have to make:

  1. airmon-ng check kill
  2. unplug adapter, plug adapter (AWUS1900) (the adapter should not light up or flash)
  3. airmon-ng start wlan0
    and its work totally great.
    I hope this helps someone.

I solved it with simple script:

#!/bin/bash
# Specify the hub location and port number
HUB_LOCATION="1-1"
PORT_NUMBER="1"
sudo airmon-ng check kill
# Turn off power to the USB port
sudo uhubctl -l "$HUB_LOCATION" -p "$PORT_NUMBER" -a off

# Wait for 1 seconds
sleep 1

# Turn on power to the USB port
sudo uhubctl -l "$HUB_LOCATION" -p "$PORT_NUMBER" -a on
sleep 1
sudo airmon-ng start wlan0

My guess is that some system service is interfering with the adapter. But this script is the easiest solution.

@morrownr
Copy link
Owner

morrownr commented Feb 1, 2024

@VeritasLibera

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 airmon-ng check kill is that airmon-ng tries to kill interfering processes whereas start-mon.sh pauses the process. I found that it is very difficult to kill some processes in that they have code to detect when they are killed and they rapidly restart. However, if the same processes are paused, there is nothing to restart and they cannot cause problems because they are not active. Try it.

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.

@morrownr

@nu11secur1ty
Copy link

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 01

TL-WN722N 02

And where is the problem? :D

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

3 participants