Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix wifi.recon.channel documentation. Preference gets reset when wifi.recon is toggled on though documentation doesn't reflect this. Might be better off as a set/get variable.
Further explanation
Bettercap ignores
wifi.recon.channel
if set before invokingwifi.recon on
.wifi.recon.channel
Must be called afterwifi.recon on
to have an impact.For example - trying to avoid channels which the network interface describes as
disabled
under example commandiw phy phy0 info |grep -E '[0-9]{4} MHz'
withwifi.recon.channel x,y,z
is entirely ignored when set beforewifi.recon on
gets issued.