09-13-2017, 10:49 AM
I just want to make sure that a non-experienced user doesn't use a silly filter and cleanup like the one mentioned above.
If you know what you are doing. just do it. at your own risk.
For all other users, you shouldn't cleanup or remove any important info from your cap file, because otherwise cap2hccapx or hcxtools can't work correctly.
There are several other packets that could help to identify a network (ESSID) etc... if you remove any important packets from the cap... the hccapx will be missing a lot of information ("hashes").
So if you are not an experienced cap/wlan (protocol) expert, do not clean the caps. If you have problems with max. number of networks analyzed by cap2hccapx, just increase the MAX to a higher value at your own risk. If you have problems with the max file upload size, just download cap2hccapx and convert the caps locally (or alternatively you could also use hcxtools locally).
If you instead know what you are doing, just go ahead and manipulate the cap file... but at your own risk.
If you know what you are doing. just do it. at your own risk.
For all other users, you shouldn't cleanup or remove any important info from your cap file, because otherwise cap2hccapx or hcxtools can't work correctly.
There are several other packets that could help to identify a network (ESSID) etc... if you remove any important packets from the cap... the hccapx will be missing a lot of information ("hashes").
So if you are not an experienced cap/wlan (protocol) expert, do not clean the caps. If you have problems with max. number of networks analyzed by cap2hccapx, just increase the MAX to a higher value at your own risk. If you have problems with the max file upload size, just download cap2hccapx and convert the caps locally (or alternatively you could also use hcxtools locally).
If you instead know what you are doing, just go ahead and manipulate the cap file... but at your own risk.