search

v1s1t0r1sh3r3 / airgeddon

This is a multi-use bash script for Linux systems to audit wireless networks.
GNU General Public License v3.0
6.46k stars 1.17k forks source link

having problems with 5ghz detection #583

Closed maximilien1990 closed 7 months ago

maximilien1990 commented 7 months ago

so basically i have 2 wifi cards which i know guaranteed for a fact that have both 5ghz and 2.4hgz connectivity. except for some reson when i launch airgeddon, it says only 2.4 ghz.

heres my iw list output.

Wiphy phy3 wiphy index: 3 max # scan SSIDs: 4 max scan IEs length: 2243 bytes max # sched scan SSIDs: 0 max # match sets: 0 Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Device supports RSN-IBSS. Device supports AP-side u-APSD. Device supports T-DLS. Supported Ciphers:

as you can see there is 5ghz but airgeddon gives me

***** Interface selection ** Select an interface to work with:

  1. eth0 // Chipset: Intel Corporation Ethernet Connection
  2. wlan0 // 2.4Ghz // Chipset: Intel Corporation Cannon Lake PCH CNVi WiFi
  3. docker0 // Chipset: Unknown
  4. wlan1 // 2.4Ghz // Chipset: MediaTek Inc. WiFi
  5. wlan1mon // 2.4Ghz // Chipset: MediaTek Inc. WiFi

any idea how i can fix this?

thank you for reading

cjb900 commented 7 months ago

Nothing here is very helpful for your issue. Post a screenshot of running this command sudo airmon-ng --verbose

OscarAkaElvis commented 7 months ago

I know what is happening here. It's easy to fix... for some reason, the frequencies shown on your iw command have decimals. Something that I never saw before. So the grep command airgeddon is doing to check if the card is supporting the band is failing.

No idea about if is because your chipset or if is because your O.S. or maybe iw command version... no idea... omg, why people is not filling up the issue creation template? It's there for a reason... to save time and avoid now me asking you what O.S. are you using.... 😠

Anyway... airgeddon is doing this:

if iw phy "${1}" channels 2> /dev/null | grep -i "5180 MHz" > /dev/null; then

But your output has this: 5180.0 MHz instead of the usual 5180 MHz.

As I said... no idea about in what conditions the output is different. To know your O.S. would help, and to know the chipset of your cards (launch airmon-ng --verbose to check it). To check your iw version the command is iw --version. Please, paste all of this data.

Anyway, I improved the grep command to work on both cases, like:

if iw phy "${1}" channels 2> /dev/null | grep -Ei "5180(\.0)? MHz" > /dev/null; then

I pushed it to dev branch (v11.30), so you can test it.

crackedpotato007 commented 6 months ago

I am on Kali 2024.1, airgeddon V11.22. My freqs are non decimal and I am getting this issue,will attach iw list output in next comment

crackedpotato007 commented 6 months ago

https://sourceb.in/390uYxk9JI

OscarAkaElvis commented 6 months ago

It's not possible. The grep command is matching with your output. Anyway, did you try using dev branch?

Please, join our discord server to keep checking. You can find invitation link at wiki on contact section.

bogdanwebdeveloper commented 5 months ago

Can confirm the latest dev branch works and solves this problem