Aircrack-ng forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Aircrack-ng 1.7 release

Sorry Guest, you are banned from posting and sending personal messages on this forum.
This ban is not set to expire.
Pages: [1] 2 3 ... 10
 1 
 on: December 05, 2022, 03:36:48 pm 
Started by misterx - Last post by misterx
Mostly due to the maintenance needed to keep it up, we're moving the forum to the GitHub Discussions.

This forum will be become read-only and we'll be converting it to a static site so that the existing links to it still work.

 2 
 on: November 24, 2022, 08:59:22 pm 
Started by Elik77 - Last post by misterx
It's not possible. IVs are just part of some of the frames.

Well, it's possible but pointless as all the frames would be pretty much identical except the IV section.

 3 
 on: November 24, 2022, 08:23:13 pm 
Started by Elik77 - Last post by Elik77
Hello...please help...
How to convert ivs file to cap?


 4 
 on: November 17, 2022, 03:26:28 am 
Started by pandoragami - Last post by pandoragami
Quote
Well, you may want to look into why it went into read only mode. I have never seen that happen in all the years I've used Linux.

Since, as you say, it went into read-only mode, it is expected there will be errors related to I/O. And thus, this is not a bug: the code expects to have a writable filesystem, which is out of our control.

Thanks for the reply, I guess I'll look into your advice since it makes sense although I cannot think of why the system goes into read-only mode in the middle of an update.The only other time I've had this happen is when my HDD was failing but it only does this when this piece of software is updated. I don't blame you guys though it's just weird. Anyways I'll try to figure it out and if I do find something I'll post it. Could be months from now.

Cheers!

 5 
 on: November 16, 2022, 06:51:34 pm 
Started by pandoragami - Last post by misterx
Well, you may want to look into why it went into read only mode. I have never seen that happen in all the years I've used Linux.

Since, as you say, it went into read-only mode, it is expected there will be errors related to I/O. And thus, this is not a bug: the code expects to have a writable filesystem, which is out of our control.

 6 
 on: November 15, 2022, 04:30:40 pm 
Started by pandoragami - Last post by pandoragami
Hello,


So basically I was updating the version of this repo on my Xubuntu box

https://github.com/aircrack-ng/rtl8812au

and during the update my system went into a read only mode situation where I wasn't able to copy and paste the output from the bash shell
and I took photos of it. I was able to reboot my machine and avoid initramfs. Once reboots I used the dpkg --configure a command and everything
fixed itself. I've had several other issues with this library before but I wasn't concerned with the previous errors thinking it'll go away and it's a one time
deal.


 7 
 on: November 14, 2022, 11:07:04 pm 
Started by berzkk - Last post by berzkk
Thank you so much!, i would take you recommendation that use other adapter!.

 8 
 on: November 14, 2022, 08:46:16 pm 
Started by berzkk - Last post by misterx
If you see an interface for that adapter, the firmware failed to load are pretty irrelevant.

It just tries a bunch of firmware in a specific order until it finds one that exist (and you can see it in your logs: 72, 71, 70, 69, ...).

It seems to be a known issue: https://github.com/aircrack-ng/aircrack-ng/issues/2330 and until the issue is found and fixed, I'd recommend using another adapter.

 9 
 on: November 14, 2022, 07:47:45 pm 
Started by berzkk - Last post by berzkk
Wi-Fi 6 AX200 is my wifi adapter

i check another post who occured the same and i run dmesg

and it shows:

[    4.293503] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[    4.309357] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-72.ucode (-2)
[    4.309362] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[    4.309370] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-72.ucode (-2)
[    4.309372] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-72.ucode failed with error -2
[    4.309384] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-71.ucode (-2)
[    4.309480] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-71.ucode (-2)
[    4.309481] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-71.ucode failed with error -2
[    4.309490] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-70.ucode (-2)
[    4.309497] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-70.ucode (-2)
[    4.309498] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-70.ucode failed with error -2
[    4.309506] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-69.ucode (-2)
[    4.309513] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-69.ucode (-2)
[    4.309514] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-69.ucode failed with error -2
[    4.309522] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-68.ucode (-2)
[    4.309529] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-68.ucode (-2)
[    4.309530] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-68.ucode failed with error -2
[    4.309537] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-67.ucode (-2)
[    4.309544] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-67.ucode (-2)
[    4.309545] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-67.ucode failed with error -2
[    4.309553] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2)
[    4.309559] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-66.ucode (-2)
[    4.309561] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2
[    4.309568] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2)
[    4.309575] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2)
[    4.309576] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2
[    4.309583] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2)
[    4.309590] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2)
[    4.309591] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
[    4.310814] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode
[    4.310824] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
[    4.310833] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    4.311028] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    4.311035] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)

 10 
 on: November 14, 2022, 07:21:32 pm 
Started by berzkk - Last post by berzkk
hi everyone!, i am a newbie on linux , and im learning using aircrack-ng (testing on my own red)... but i have been stuck with one thing /    aireplay-ng --deauth {x} -a {bssid} wlan0mon. causes that my kali freeze without respond. what should i do? thank you all!.

im runing kali on dual boot, i disable fast boot and secure boot.
note asus rog.

Pages: [1] 2 3 ... 10