At least for the initial, meta-data gathering phase of the demo, selecting an adapter that is being used to provide an Internet connection will limit the effectiveness of the demo. (At a minimum, it will bias discovered devices toward those on the same channel as the WiFi access point to which it is connected.)
I propose an OK/Cancel dialog, when "Start" is pressed, if the selected adapter is active (has an IP address?).
Most likely, we will need something similar for the second phase of the demo, though I have not yet identified a reproducible case in which sending deauth packets with an in-use adapter causes problems. Presumably, issues will arise If the adapter is connected to a WiFi network that is different from the one selected for the sniffing phase of the demo (or, at a minimum, when it is connected to a WiFi network on a different channel).
For this case, perhaps we can add an appropriate warning to the WPA password dialog?
At least for the initial, meta-data gathering phase of the demo, selecting an adapter that is being used to provide an Internet connection will limit the effectiveness of the demo. (At a minimum, it will bias discovered devices toward those on the same channel as the WiFi access point to which it is connected.)
I propose an OK/Cancel dialog, when "Start" is pressed, if the selected adapter is active (has an IP address?).
Most likely, we will need something similar for the second phase of the demo, though I have not yet identified a reproducible case in which sending deauth packets with an in-use adapter causes problems. Presumably, issues will arise If the adapter is connected to a WiFi network that is different from the one selected for the sniffing phase of the demo (or, at a minimum, when it is connected to a WiFi network on a different channel).
For this case, perhaps we can add an appropriate warning to the WPA password dialog?