search

Ragnt / AngryOxide

802.11 Attack Tool
GNU General Public License v3.0
957 stars 47 forks source link

thread 'main' panicked #32

Closed jakkpotts closed 5 months ago

jakkpotts commented 5 months ago

thread 'main' panicked at src/main.rs:1118:9: Channel is None. Current Frequency: Frequency { frequency: None, width: Some(ChanWidth20Noht), channel: None, pwr: Some(2000) } note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

To Reproduce Steps to reproduce the behavior: sudo angryoxide --whitelist ~/working/config/whitelist.txt --interface wlan0 -b 2,5

Hardware (please complete the following information):

Additional context about 10 seconds into launching the application, main thread panics and app terminates with the above output

Ragnt commented 5 months ago

This is the same error as:

https://github.com/Ragnt/AngryOxide/issues/27#issuecomment-1995191340

But seeing this with a PAU0D is alarming, as that means this isn't a driver issue.

What version of Kali is this? What kernel version?

jakkpotts commented 5 months ago

This is the same error as:

#27 (comment)

But seeing this with a PAU0D is alarming, as that means this isn't a driver issue.

What version of Kali is this? What kernel version?

6.6.9-arm64 // Kali 6.6.9-1kali1 (2024-01-08) // aarch64 GNU/Linux

I should have noted -- that it seems like this error only happens when 5ghz bandwidth (in combination with 2ghz) is specified in the runtime arguments. If I run with ".... -b 2" there is no issue.

edit: Scratch that, it does also result in an error with ".... -b 2". I ran the tool for quite a long time using "... -c 1,3,6,7,11" and yielded very useful hashes. Seems like something is happening when specifying the entire bandwidth. In the last tab of the app, right before it crashes I see "Error" in red pop up, I'm trying to grab a screenshot of it.

Untitled Of course, now it seems to be running just fine. This instance was "... -b 2"

SCR-20240324-pbfj

Then, run with "... -b 2,5"

Ragnt commented 5 months ago

Ah- the network down error is usually caused by another process trying to take over the interface.

Try to kill wpa_supplicant and network manager, see what happens.

Since you are on Kali, try just running sudo airmon-ng check kill and run again, see if it happens.

jakkpotts commented 5 months ago

Yes indeed, that as well. I opted to change the interface's name and add an entry to the NetworkManager service config file to ignore any interfaces with the specified name.