Fix failed to arm interface on 5GHz by distinguishing band suffixes #433
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Description Bug Description: When running Wifite2 with --hcxdump on 5GHz channels (e.g., channel 36, 40, 149), hcxdumptool fails to start with the error: failed to arm interface. Root Cause: In wifite/tools/hcxdumptool.py, the previous code blindly appended the 'a' suffix (indicating 2.4GHz) to all numeric channels. Channel 6 becomes 6a (Valid for 2.4GHz). Channel 40 becomes 40a (Invalid: implies channel 40 on the 2.4GHz band). This causes hcxdumptool (or the underlying driver) to reject the command because channel 40 does not exist on the 2.4GHz band. The Fix: I have refactored the channel logic to remove the forced 'a' suffix for all channels. The code now checks the channel number to apply the correct band suffix: Channels <= 14: Appends 'a' (2.4GHz). Channels > 14: Appends 'b' (5GHz). This ensures valid channel arguments are passed to the tool for both frequency bands.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Bug Description: When running Wifite2 with --hcxdump on 5GHz channels (e.g., channel 36, 40, 149), hcxdumptool fails to start with the error: failed to arm interface.
Root Cause: In wifite/tools/hcxdumptool.py, the previous code blindly appended the 'a' suffix (indicating 2.4GHz) to all numeric channels.
This causes hcxdumptool (or the underlying driver) to reject the command because channel 40 does not exist on the 2.4GHz band.
The Fix: I have refactored the channel logic to remove the forced 'a' suffix for all channels. The code now checks the channel number to apply the correct band suffix:
This ensures valid channel arguments are passed to the tool for both frequency bands.