-
Notifications
You must be signed in to change notification settings - Fork 147
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
(Request) Aircrack NG (falcon tools) 6E channel/freq scans #68
Comments
I think if aircrack scans it, it should come out. I don't have any 6E here yet to test it out with, but may get some soon. For the falcon start, there isn't a param or anything for it since there's a requirement for the monitor mode on the card. You could just use curl or wget and trigger it in a launch script after you start the agent. That's probably the easiest solution. |
I was thinking maybe a parm or like you mentioned, maybe something additional like the curl that would put the elasticsearch py agent automatically into monitor mode (if supported) would allow little to no interaction by the user to setup the agent in “falcon” mode. |
Some good news here on aircrack-ng and 6e channels. A new release includes the ability along with wpa3 etc. https://aircrack-ng.blogspot.com/2022/05/aircrack-ng-17.html?m=1 |
Looks like you have to specify specific channels for now though “sudo airodump-ng wlan1mon -w 6E_test -C 6115”. Maybe an option could be added to the Falcon GUI to set specific channels on/off when other then band scanning is needed. |
Can the ability to scan 6E (using compatible cards) be scripted in? I haven’t looked closely yet, but according to this post it should be possible for aircrack to be set to frequency in MHz, maybe that would require a manual table of info to scan through? Or maybe aircrack will have a 6e band added soon.
aircrack-ng/aircrack-ng#2205
Also,
Would it be possible for the sparrow-WiFi agent to start with the falcon mode of scanning enabled? Meaning without having to connect with a GUI to activate it?
The text was updated successfully, but these errors were encountered: