Aircrack-ng forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Aircrack-ng 1.6 release

Pages: [1] 2 3 ... 10
 1 
 on: June 19, 2021, 04:25:46 pm 
Started by Useruser1 - Last post by misterx
1. Just a driver not implementing a feature, but not necessarily a problem. rtl8187 does this, but monitor mode works.
2. As with all unusual hardware-related issues, always check dmesg to see if there is some messages related to the driver.

What driver does this card use? This is displayed with airmon-ng.

 2 
 on: June 19, 2021, 07:48:09 am 
Started by Useruser1 - Last post by Useruser1
Hello guys,

I´m a newbie to aircrack and I bought the following wireless usb adapter TP-LINK TL-WN823N.

It has been found by kali and I also can start the monitor mode. I have 2 special questions:

1. after starting monitor mode the information in 'iwconfig' changes also to 'monitor mode' and I get a notification message that the monitor mode is enabled now BUT the name of my wlan0 doesn´t change to wlan0@mon. Does this point to a problem?

2.When I´m searching for networks with command "airodump-ng" I can´t find anyone. Can this relate to a wrong chipset of the stick? Because monitor mode seems working fine.

P.S. I also killed all processes and changed the NetworkManager.conf regarding to some recommendations in the internet. But nothing worked...

Please help! I´m not sure to buy a different stick.

 3 
 on: June 16, 2021, 12:29:53 am 
Started by weatherman - Last post by misterx
Likely a wireless card (hardware) limitation. FYI, you responded to a 3+ year old thread.

 4 
 on: June 15, 2021, 08:39:54 pm 
Started by weatherman - Last post by MAXPG
I had the same issue, only capturing 2 of 4 out of the packets. I was able to capture all 4 when I used my kindle with the WiFi. My guess is that it has limitations based on what devices are connected.

 5 
 on: June 13, 2021, 06:14:25 pm 
Started by scorpius - Last post by scorpius
Yes, iw dev shows that it actuallly enters monitor mode. But airmon-ng stop does not return to managed. Also, with the latest build from github, I replaced the airmon-ng script with the one from 1.6 and all works fine.

 6 
 on: June 11, 2021, 10:32:16 pm 
Started by scorpius - Last post by misterx
So, it's not related to the Kali version, but only the airmon-ng version. Something changed between 1.6 and now.

One thing to note, the adapter is correctly in monitor mode, and capture works just fine, regardless of the name of the interface.

Bug report: https://github.com/aircrack-ng/aircrack-ng/issues/2245

 7 
 on: June 11, 2021, 12:40:26 am 
Started by Fpa - Last post by misterx
You first have to isolate the handshake, then parse the different items, as they are spread over several frames. You'll have to look into aircrack-ng source code.

 8 
 on: June 10, 2021, 05:42:51 pm 
Started by Fpa - Last post by Fpa
Umm anyone know how to fix this method??
using popen_noshell_

use wpa_passphrase program like so... but with fork threads...
"wpa_passphrase essid passphrase"
Code: [Select]
popen_noshell_set_fork_mode(POPEN_NOSHELL_MODE_POSIX_SPAWN);

char *exec_file = (char *) "wpa_passphrase";
char *arg1 = g_essid;
char *arg2 = g_key;
char *arg3 = (char *) NULL; /* last element */
char *argv[] = {exec_file, arg1, arg2, arg3};
/* NOTE! The first argv[] must be the executed *exec_file itself */

  fp = popen_noshell(argv[0], (const char * const *)argv, "r", &pclose_arg, 0);

parse remove the output
Code: [Select]
strcpy(pmk, replace_str(g_pmk, " psk=","")); //Parse

call calc mic
Code: [Select]
calc_mic( g_keyver, stmac, bssid, anonce, snonce, eapol, pmk, ptk, mic ); //HELP < NOT RETURNING PROPER MIC WITH POPEN METHOD

how do i read the data from .cap file for keyver, stmac, bssid, anonce, snonce, eapol, ... ?
any help would be greatly appreciated!!! please help fix calc_mic()

 9 
 on: June 09, 2021, 08:17:39 pm 
Started by scorpius - Last post by misterx
If other cards are working, then there is more chance it is a bug in the driver. Is there anything in dmesg?

You mention you don't have network manager running. Did you kill them?

You likely want to try different revisions of aircrack-ng between 1.6 and that revision (I'm assuming it is this specific revision - 91820bc). You likely want to check the ones that changed airmon-ng, starting from b98ceff on March 20th, which is the first change after 1.6.

 10 
 on: June 09, 2021, 03:28:21 pm 
Started by scorpius - Last post by scorpius
I just checked with my working setup and upgraded aircrack-ng via apt to 1:1.6+git20210130.91820bc-1, and the problem now exists. It seems to be something between 1.6-4 and 1.6+git20210130.91820bc-1 that introduced the problem/bug.

Pages: [1] 2 3 ... 10