Aircrack-ng forum

Please login or register.

Login with username, password and session length
Advanced search  


Aircrack-ng 1.6 release

Pages: [1] 2 3 ... 10
 on: July 19, 2021, 09:47:41 pm 
Started by DarkAngel666 - Last post by misterx
You can't use it with Kali, as you access this device through the network. So, you'd have to access it, and find how to put it in monitor mode. That might involve flashing it with OpenWrt.

Why aircrack only supports low power low gain standard wifi cards?

The amount of power of a wireless card doesn't matter. All that matters is that if it has a driver.

Can i set it in monitor mode to get handshakes using wireshark?

If you can access it, and have enough space to install X and wireshark on that device, yes, you could remote in. However, you probably want to use tcpdump/tshark to forward traffic to your computer, as this device doesn't have much power/space.

Can some one make a script to use this kind of devices in aircrack-ng?

Scripts already exist (such as wifite). All you have to do is have a usable Linux and tools on the device.

like a universal script?.

That isn't really possible, each device is different. There isn't a universal script to install OpenWrt on different devices because they're all different. You could hire someone to build such script for a subset of devices.

 on: July 19, 2021, 01:10:17 am 
Started by DarkAngel666 - Last post by DarkAngel666
Hi, I have this high power device " Tp link CPE model TL-Wa5210g" and i was thinking how to put this device in monitor mode to use with aircrack-ng in kali linux.
Why aircrack only supports low power low gain standard wifi cards?
Can i set it in monitor mode to get handshakes using wireshark?
Can some one make a script to use this kind of devices in aircrack-ng?
like a universal script?.

 on: July 17, 2021, 07:48:20 am 
Started by zua - Last post by zua

I am trying to live decrypt my WPA2 wifi but can't archive my goal (since 3 months  :'( )

What I do :

Terminal 1 :
Code: [Select]
sudo airmon-ng
sudo airmon-ng check
sudo airmon-ng check kill
sudo airmon-ng start wlp3s0 11
sudo airodump-ng wlp3s0mon --essid 'MySSID' -c 11

Terminal 2 :
Code: [Select]
sudo airtun-ng -a 'A4:XX:XX:XX:XX:D6' -p 'MyPSKey' -e 'MySSID' wlp3s0mon
gives :
created tap interface at0
WPA encryption specified. Sending and receiving frames through wlp3s0mon.
FromDS bit set in all frames.

Terminal 3 :
Code: [Select]
sudo ifconfig at0 up
sudo tcpdump -v -i at0

Now I on/off my iPhone connected to the wifi

Terminal 2 (airtun-ng command) shows correctly the WPA handshakes
WPA handshake: C4:XX:XX:XX:XX:BC

Terminal 3 (tcpdump command) only shows some unknown packets and some IP6 packets.
09:15:34.666669 c4:xx:xx:xx:xx:bc (oui Unknown) > a4:xx:xx:xx:xx:d6 (oui Unknown), ethertype Unknown (0x0a00), length 105:
        0x0000:  1000 0000 0000 0000 0100 0000 0000 0000  ................
        0x0010:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0020:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0030:  0000 0000 0000 0000 0000 0000 0000 0000  ................
        0x0040:  0000 0000 0000 0000 0025 92cc 4e66 3e91  .........%..Nf>.
        0x0050:  8c0e 3ca9 3f41 6315 5d00 00              ..<.?Ac.]..
09:15:38.956948 IP6 (flowlabel 0xeeba0, hlim 255, next-header UDP (17) payload length: 53) MyPCIamUsingNow.mdns > ff02::xx.mdns: [udp sum ok] 0 [2q] PTR (QM)? _ipps._tcp.local. PTR (QM)? _ipp._tcp.local. (45)
09:17:35.260760 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) MyPCIamUsingNow > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 16
          source link-address option (1), length 8 (1): ca:xx:xx:xx:xx:ac

I am trying to access some new websites on my iphone in order to capture DNS requests ... but nothing shows up
No traffic releated to the iPhone

Any idea ?  :-\
Thanks !

 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.

 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.

 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.

 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.

 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.

 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:

 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.

Pages: [1] 2 3 ... 10