Wireshark bluetooth controller dissector plugin #118
Merged
Conversation
This file contains 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
fengjixuchui
added a commit
to fengjixuchui/Nintendo_Switch_Reverse_Engineering
that referenced
this pull request
Feb 2, 2021
Merge pull request dekuNukem#118 from Poohl/nxbt_wireshark_plugin
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.
Hi, i am working on understanding and reproducing the MCU's NFC functionality (mart1nro/joycontrol#89) and in the process wrote a wireshark plugin to dissect the Bluetooth communication between Joycon and switch.
I know that something similar already exists for traffic captured via usb implemented in LUA but i couldn't get the LUA API to do as I wanted, so this is implemented in C (also no
elifchains).If you want I can also supply a compiled version for ubuntu x64 that should be just as simple to use as the LUA one.
Currently the following is dissected:
and these only mark the appropiate fields:
Beyond that the main thing obviously missing is marking of known constants as "expected".
The traffic this dissects is captured by using a PC running wireshark as proxy between the Switch and a Joycon (Pro Controller works, but overloads my laptops's bluetooth controller)