-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
A few bugs #313
Comments
Hi, you've violated our policy talking about other tools here.... but I will not close it directly this time (is what is supposed must be done due an issue creation policy violation)... the people say sometimes I'm a hard bone as admin... 🙄 And I must add that I saw you even didn't starred our repo... I must admit that I don't like people who is spending time to write long issues but is not able to spend a second to click on "star" to support the project... yeah I know, maybe I should add it to the issue creation policy... Anyway, I'll try to answer to you. Yeah, as you said this chipset is blacklisted... so consider this answer as an "extra bonus".
I'll leave this open for a while maybe somebody could want to add some interesting data... but you must understand that we do our best, spending our own money on our free time to give to the community a handy tool compatible with many Linux and with many cards. We try to do the best to work with a standard "base line" and we can't start making exceptions with crappy cards/chipsets. I think the plugins system will be the solution for many problems. We need to wait! 😸 |
Thanks for your detailed answer! I starred the repo but keep in mind that I was told about that tool yesterday :) Sorry for mentioning other tools but it was the only way to explain what happened. As you have said, the problem is coming from that airmon compatibility check, that's probably the case. I don't know which driver doesn't support it, so I can test but anyway, that plugin will be amazing. In that time, I will try to figure out the deauthorization thing. Here is a link with a working solution: https://github.com/wi-fi-analyzer/fluxion/blob/master/fluxion.sh#L1164. |
Yeah, I'm glad you finally got some positive results deauthing... remember to try mdk3 instead of mdk4!!! Regarding the card... check the compatible list from wiki. You'll find a Panda card pretty easy to find on any online shop like amazon or ebay and it supports 5ghz!! |
Hi @OscarAkaElvis, I am the user of the Realtek RTL8812AU (AWUS036ACH). I just got it this week. Thank you for your long response to the thread. This sentence caught my eye:
I had been searching Google for many hours and had consistently seen the AWUS036ACH recommended for Kali Linux over and over again. That is why I had purchased it. You are indeed correct it was quite an expensive card. Do you think it is worth waiting for some sort of patch, or do you recommend that I return it and go for an alternative? Thank you for your time :) |
If you still have the opportunity of return it and get your money refund, do it! at least if you plan to use airgeddon. If you plan to use other tools maybe it could work, I can't tell... never used fluxion to be honest. |
I am still able to return it. What card what you recommend instead? |
Check the list of airgeddon compatible cards at Wiki: https://github.com/v1s1t0r1sh3r3/airgeddon/wiki/Cards%20and%20Chipsets It seems some of them (5Ghz listed Alfa cards) are hard to find. But there you'll find also a Panda wireless card compatible to 5Ghz and pretty easy to find on any online shop (Amazon, Ebay, etc). |
Ok guys, i'm going to close this. Thanks for your comments. |
Ding ding ding!!! your dreams come true: https://github.com/OscarAkaElvis/airgeddon-plugins |
What is your airgeddon version?
9.23
What is your Linux O.S. and which version?
Kali Linux 2019.3
Which is the chipset of your wireless card?
Realtek RTL8812AU (AWUS036ACH)
Describe the issue and the steps to reproduce it
I know that this chipset is on your blacklist but still it's worth reading what I wrote below.
As some people suggested, driver v5.2.2 works fine. https://github.com/aircrack-ng/rtl8812au/tree/v5.2.20
Problems:
When I attempt to handshake my own network, it doesn't throw me out of the Wi FI connection, so it can reconnect my device and successfully handshake afterwards. Only AWUS036NHA and Fluxion 2.9 is working fine (https://github.com/wi-fi-analyzer/fluxion) are it throws me out as well as it automatically handshakes after that. Note that Fluxion 5.9 is not working either.
The problem is that if it doesn't deauthorize me properly (throw me out)), it won't succeed to handshake at all. I know that because I tested it a few times by disconnecting my device manually and then reconnecting while it is still handshaking. It handshakes right after I reconnect.
aireplay-ng -9 wlan0
in a separate terminal window while I'm handshaking. I think the problem is inconsistency between airgeddon's commands and aircrack's.The driver itself is working fine when you manually type stuff but not when you do that through airgeddon. Is there any way to handle this? The second problem I mentioned is not related to that problematic chipset, what about it?
The text was updated successfully, but these errors were encountered: