Wifi tools break my interface? [SOLVED]

[blackout.dev]

Greetings,
   On a fresh install of Backbox, updated programs, every time I attempt to do some wireless (what have you), my AWUSO36H Alfa card breaks! I've used this card in the past, on backbox, with success. But with this install, the breakage always occurs a few minutes after running wash or reaver. If I attempt to restart the interface I get an "operation not possible due to rfkill." I'm on a desktop computer btw.

rfkill list all, reports a hard block on 2: phy2: Wireless LAN. Soft blocked is a no. The online fix, rfkill unblock wifi doesn't do much, I have to physically disconnect the card and reconnect it to remove this block.

Reaver version is 1.4. I've tried feeding reaver mon0 and wlan0, one at a time, but both broke the same. I tried killing all the programs that airmon-ng reports could cause a problem and that doesn't make a difference either.

Maybe a list of steps would help?
1. sudo -s
2. disable networking
3. airmon-ng start wlan0
4. reaver -i -b -e -c -vv or wash -i
5. two minutes later, the program hangs

               Thank you,
                       -dev

[blackout.dev]

Welp, thanks for looking guys. If there is any other info you need to assist, feel free to scream!

[ZEROF]

Hi,

1st i don't see how this issue have something with BBox. This is reaver issue if you ask me (or not). Did you try to install last updated and patched drivers (for this check Howto forum i made topic about it)? And before using monitor mode run airmon-ng check kill command if you want to stop networking, that is  in right way.

And if you don't have any vulnerable networks in your hood reaver will stop after few min., that is normal.

[blackout.dev]

Hi,

1st i don't see how this issue have something with BBox. This is reaver issue if you ask me (or not). Did you try to install last updated and patched drivers (for this check Howto forum i made topic about it)? And before using monitor mode run airmon-ng check kill command if you want to stop networking, that is  in right way.

And if you don't have any vulnerable networksin your hood reaver will stop after few min., that is normal.

I don't know what this issues relates to exactly. I only figured you were a human willing to assist me and this was a place for discussion. That is all.

Thanks for the check kill argument.

The target network was previously cracked via the same method with a connection above 70% and a strong link quality. That is not the issue.

Drivers are up to date.

This problem still exists.

[b4d_bl0ck]

blackout.dev,
as you can guess an hard block implies a phisical switch to be turned off. So such an error, with the kernel reporting a turned off button while it is actually turned on, is a bit weird. It may be the driver, but anyways it's strange it happens after a while using some tools. Anyways that has nothing to do with network interfaces (and should have nothing to do with particular tools as well, but...)
Maybe you need to investigate in log files when the wireless adapter stops working.

Bye!