-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hcxdumptool new style #355
Comments
This options (--filterlist_ap=my filter.txt --filternode=3 or --enable_status=1) have been removed since v6.3.0. More information is here: as well as here: and in changelog: Closed,this report here, because this changes are wanted and announced. |
Option "enable_status=1" has been replaced by "rds=1" and the slow waterfall display has been replaced by a fast split screen. |
A typical command line (scan all frequencies supported by the interface) is In case of filtering: In case if using a single channel, e.g. channel 1: Scan only main channel 1, 6 and 11 on 2.4GHz band: Or any other combination of the new options. |
Quick follow up question. On nethunter and kalilinux pc, any command with a "--" before it throws "unrecognised option " example --disable_deauthentication or --do_rcascan |
This option "--do_rcascan" has been replaced by "--rcascan=active".
Running the new style, everything should be fine:
|
Also attack.bpf is empty. Use command hcxdumptool -m wlan0 |
Has the man page not been updated yet |
Command line is wrong.
correct command line:
|
The default man page of hcxdumptool points to "--help": If your manpage is different it is not created by me. |
Sorry in the command line I do add "addr1" |
Not my manpage. |
Arch Linux don't need a manpage (like Debian). So it is not installed by default and makefile doesn't have an entry to install this manpage. Maybe you have an old manpage (if you have not uninstaqlled the old version before you have installed the new verion) or a manpage created by a package maintainer. |
Ahhh so confusing lol. |
Forget last. My mistake. |
tcpdump will show this error if the interface is not in monitor mode and not up. |
If the target AP is not on channel 1a, 6a or 11a, don't forget to set the operation channel of the AP by option "-c" or scan all frequencies by option "-F". |
I didn't insert wlan before addr3 just -I wlan0 addr3 |
Ok |
My chanel is 11 so "-c 11a " is for 2.4ghz |
Please also notice that running this filter: You'll get a warning (missing frames) by hcxpcapngtool when converting the dump file to hc22000 format because undirected proberequest frames are filtered out, too. To avoid that, add a BROADCAST MAC to your filter: Additional you can tell hcxdumptool to terminate if you got a PMKID or a handshake:
|
Would this adaptor work Alfa Network AWUS036AC Long-Range Dual-Band chipset RTL8812AU both bands? |
The RTL8812AU driver is not part of the stock Linux kernel. Please read the adapter section of README.md (recommended and not recommended chipsets/drivers). Please also read this: There is a difference between addr1, addr2, addr3 and add4:
https://www.geeksforgeeks.org/ieee-802-11-mac-frame/ |
Your a legend thanks so much for your help. Is there a dule band adaptor you would recomend. Currently using the tplink tl wn722n 2.4ghs. |
Is there any other solutions to single out a specific ap to attack this dosent seem to work like you said. |
ALFA AWUS036ACM Give me a few minutes to run a test. |
here we go:
build filter:
For this test we do not need frames addressed to BROADCAST MAC and they are filtered out. run attack against target test AP:
conver to hc22000 format:
hcxpcapngtool has detected the absence of frames addressed to BROADCAST MAC and told us that (missing frames). Try to recover the PSK:
For this test I configured a very simple PSK 12345678 which was successful recovered by hashcat. Conclusion:
The PSK has been successful recovered. |
You will not be able to compile this outdated driver. |
Best give up then I guess. Is it safe assume that esfile explorer pic I sent is compatible drivers as my tilink driver is there and that worked out the box no problems? |
Tplink* |
Installing out of tree driver isn't easy.
Running is third party drivers means that you will run into problems. |
Is their a file with the stock kernal drivers in nethunter? |
Stock drivers means that the driver comes with the Linux kernel: |
That's the same one iv been trying to install |
First of all you have to fix your configuration problems: An example:
So my api headers should be on 6.x:
|
Is there a way to find what drivers came preinstalled with my nethunter kernel |
Should give a list like this:
and
Should show you the MediaTek drivers: |
Can't work, because it is a Linux (only) example. BTW: |
I used the nethunter installer for my phone makecsnd model so should be the official one |
What is the output of uname -r |
and what is the output of |
Configuration error: Headers and kernel do not match. |
So nothing can be done to change it except maybe use nethunter installer to make a new kernel and flash it. |
I don't know how to fix this on KALI nethunter, because I don't know how this happened. |
That is possible. |
Hcxdumptool was working for the bpf filter mode but that's all I tested. Guess I'm gonna have to wipe and reinstall everything. Will let you know the results. |
Kernel and API should match:
kernel == 6.x and API header == 6.x |
Update. Reinstalled a android and rooted installed kali nethunter and installed a kernel from the nethunter project and still the cyberknight777 kernel wich I'm pretty sure came from the nethunter installer project. |
It is mandatory to make sure that KALI Linux api header match to your kernel. |
It's exactly the same as before. Really need help from someone who maintains nethunter installer project. And need to find the best way to uninstall nethunter without having to factory reset my phone and start from the beginning every time. |
Need help with hcxdumptool on nethunter. When running command "hcxdumptool -i wlan0 -w pmkid.pcapng" it runs and pumps in pmkid.pcapng but if i add any more to the command like --filterlist_ap=my filter.txt --filternode=3 or --enable_status=1 it throws "2 errors during run time" "failed to arm interface" .
The text was updated successfully, but these errors were encountered: