-
Notifications
You must be signed in to change notification settings - Fork 185
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
5Ghz Testing Issues #33
Comments
wlan0mon = AWUS036NHA
When i check with ps to see if any process is in the background I don't see anything besides the bash shell that is currently checking with ps (hope that last bit made sense) |
Sounds like this is an issue with the AWUS036ACM on Linux itself. Have you tried using the AWUS036ACM as a normal Wi-Fi dongle? That is, connect it to the computer, and use the normal Linux network manager to connect to a Wi-Fi network. |
sudo ip link set wlan0 down I did this for both AWUS036ACM cards. Then I run the python enviroment. |
MY_FnF_scripts.zip - This is to be used within the LiveOS image Attached is a zip file of a few FnF scripts that I've made. This should be used after the python environment is launched. |
Glad to hear you got it working! So the summarize the issue, since this may be useful for others: the AWUS036ACM was unable to see the 5GHz SSID that was being tested when using the live OS (i.e. the build-in network manager couldn't see it). Other 5GHz networks could be seen though. When executing |
Yes sir. It seems that you have to manually set the frequency and channel for 5Ghz bands to be targeted by the PoC. |
Previously I have been using a AWUS036NHA and I wanted to switch to testing 5Ghz channels so I got a AWUS036ACM. The provided ubuntu os was able to detect my device and I was able to set it into monitor. mode. However when trying to run a simple command such as
./fragattack.py wlan0mon pin
I get the following error:Now I have been doing these tests for a while so Im very confident in my setup however just when swapping the cards from the NHA to the ACM this error occurs. Any thoughts or fixes?
Not only does the command fail but it seems any other command sent after the failed command freezes the machine and requires a reboot.
The text was updated successfully, but these errors were encountered: