ERROR: GET_INTERFACE_STATUS 2

[jakkpotts]

Describe the bug
Hard to say, I was running angryoxide on a raspi02w in the field, power bank as a power supply with a Panda AWUS036ACS adapter. I've noticed that when I power on the raspi in my lab, where the default wifi network is located and configured with raspi-config (on the internal wifi interface, wlan0) then configure angryoxide to run on the adapter (panda0) and leave the lab -- I've noticed errors when I return to the lab, back into the environment where the NetworkManager service manages the wlan0 (Broadcom) wifi interface. I suspect this is causing an issue.

Screenshots
I was able to pull this:

`2024-04-20 22:57:29 UTC | Info | Sending Deauth: 86763f91c5a8 => ffffffffffff
💲 Cleaning up...

                                                                ..%%%%%
                                                      ...    .%%%%%%""
                                                   .%%%%%%%/%%%%%"
                                 .....           .%%%%%%%%%%%%%%\
                            ..:::::::::::..      :;""  {_}\%%/%%%%%%..
                          .:::::::::::::::::.            {_}/{_}%%%%%%%
                         :::::::::::::::::::::            \\//    """\::
                        :::::::::::::::::::::::           \\//

---------------------....-----..--.....~------\//----
--------------__--.----...----...----..---__---\//----_
----------------...-----..--..---..-------\//-----____
---------------..--..-..----....-------\//-------
-----------------..----------.--------\//-----
----------------------------------\//------
---------------- \//
----__--____ ' \// _
__--- @ , " {_}
. '

========== Error: (GET_INTERFACE_STATUS 2) Error response received from netlink: No such device (os error 19) ==========
💲 Setting alfa0 down.
💲 Restoring alfa0 MAC back to 00c0cab5b7a8.
💲 Setting alfa0 to station mode.
💲 Stopping Threads

😈 Results:
[SBG8300-783D] : 4wHS: 1 | PMKID: 0
[RingOfSecurity-sXJM2Bdi/] : 4wHS: 1 | PMKID: 0

📦 Creating Output Tarball (oxide-2024-04-20_22-52-27.tar.gz).
Please wait...

Complete! Happy Cracking! 🤙`

** Hardware (please complete the following information):**

• raspberry pi zero 2 w
• 5.15.44-Re4son-v7+ Implement PS-POLL/REASSSOCIATION Downgrade attack #1 SMP Debian kali-pi (2022-07-03) armv7l GNU/Linux
• Interface: AWUS036ACS

[Ragnt]

Have you blacklisted the panda card in network manager? This looks to me like network manager messing with it. This could also be a edge-case in re4son, but I'm not too sure about that. Whatever is happening, it looks that the device is not found at some point when we go to check on it. That error in particular is coming directly from the kernel.

[jakkpotts]

Yes, I have created a system rule to have the panda adapter not managed by NetworkManager. Would you suggest to remove the rule and instead just kill the service before I launch angryoxide?On Apr 21, 2024, at 7:42 AM, rage ***@***.***> wrote: Have you blacklisted the panda card in network manager? This looks to me like network manager messing with it. This could also be a edge-case in re4son, but I'm not too sure about that. Whatever is happening, it looks that the device is not found at some point when we go to check on it. That error in particular is coming directly from the kernel. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Ragnt]

It's certainly worth a try. I would be interested to see what dmesg is putting out around the same time as it crashes as well.

…

On Sunday, April 21st, 2024 at 4:15 PM, Ian Fain ***@***.***> wrote: Yes, I have created a system rule to have the panda adapter not managed by NetworkManager. Would you suggest to remove the rule and instead just kill the service before I launch angryoxide?On Apr 21, 2024, at 7:42 AM, rage ***@***.***> wrote: Have you blacklisted the panda card in network manager? This looks to me like network manager messing with it. This could also be a edge-case in re4son, but I'm not too sure about that. Whatever is happening, it looks that the device is not found at some point when we go to check on it. That error in particular is coming directly from the kernel. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, [view it on GitHub](#34 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AF4YMESAMDCX4VWA6QJT5R3Y6QM6HAVCNFSM6AAAAABGRDERQ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRYGE4DKNZUGM). You are receiving this because you commented.Message ID: ***@***.***>