WEF
WEF copied to clipboard
Problem with Beacon Flood attack using Alfa AWUS036ACM
Describe the bug The wifi I'm testing on is 2.4 and 5 Gh combined. There is no effect after turning on the beacon flood attack. I checked the wlan0 information and it shows Frequency: 2.412 GHz. Is it a problem that the 5GHz antenna is not recognized?Does it not support 802.11ac protocol? But I looked at the network card and it showed 802.11 ac. I don't know where the problem is anymore.
Expected behavior There is no confusion about the names of some APs, I suspect these are 5GHz ones.
Screenshots
WEF version 1.1
System information:
- OS: kali linux Linux 6.1.0-kali5-amd64 Debian 6.1.12-1kali2 (2023-02-23) x86_64 GNU/Linux
- Network card: Alfa AWUS036ACM
Are fake APs generated?
I don't know if this attack works over 5Ghz, however it isn't 100% effective even on 2.4 Ghz
yes.But I can still connect to the previous AP. I just tested and found that 5Ghz AP points cannot be scanned. But I see that Alfa AWUS036ACM supports 5Ghz, I don't know if there is something wrong with my usage.
凬清沄淡 @.***
------------------ 原始邮件 ------------------ 发件人: @.>; 发送时间: 2023年5月24日(星期三) 晚上11:01 收件人: @.>; 抄送: @.>; @.>; 主题: Re: [D3Ext/WEF] Problem with Beacon Flood attack using Alfa AWUS036ACM (Issue #32)
Are fake APs generated?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
After I turned off the merge function and scanned the AP, I still could not recognize the 5Ghz AP information.
I may have found the problem, when I start the network card, I found that the wlan0 status changed to wlan0mon Frequency: 2.457 GHz. 5GHz did not appear. Does the start network card only enable the 2.4GHz module by default and not the 5GHz module? @D3Ext
Excuse me but I was quite busy and I updated WEF with lots of features. From my own testing it should work with no problems using 2.4 GHz, 5GHz or both. I think that only "Frequency:2.457 GHz" is displayed because iwconfig doesn't show 5 GHz. Anyway, the script now uses the iw command instead of iwconfig