Add Support for Both hciconfig and btmgmt Bluetooth Management Tools #105
+300
−23
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR adds compatibility for both legacy (hciconfig) and modern (btmgmt) Bluetooth management tools, ensuring BlueDucky works across different Linux distributions and BlueZ versions. Additionally, it includes significant improvements to connection stability and error handling.
Key Changes
Auto-detection: Works with both legacy (hciconfig) and modern (btmgmt) tools
D-Bus integration: Handles adapter properties via D-Bus for btmgmt
Connection stability: Graceful handling of connection resets (errno 104)
Retry logic: Limited reconnection attempts with progressive delays
Files Changed
Benefits
Testing
Tested on systems with btmgmt, verified tool detection, adapter settings, and payload execution.