It is the most commonly used tool for troubleshooting network issues, and it already has built-in support for hundreds of general protocols. Additionally, its extensibility is excellent, allowing you to use or write protocol parser plugins for custom application-layer network protocols. This enables you to observe the protocol content rather than a binary stream, providing convenience for troubleshooting.
Recently, while investigating a timeout issue, I took some time to write a protocol parser plugin. Currently, it supports and protocols, and it can aggregate multiple into the upper layer. It does not yet support HSF’s original TB Remoting protocol. Let’s take a look at the results.
First, the Packet List area is already able to recognize the HSF2 protocol:
HSF Request and Response
HSF’s Heartbeat Protocol
By clicking on a packet, you can view detailed protocol content in the Packet details area: HSF Request
You can see many important details of the protocol, including serialization method, timeout duration, service name, method, and parameters.
HSF Response
HeartBeat Request
The Heartbeat protocol is relatively simple, so we won’t look into the response.
The plugin is developed using Lua, and the installation is relatively simple. Here is an example for the OS X platform:
Copy the protocol parsing script to the directory
Edit the file and configure it to ensure Lua support is enabled
At the end of the file, add
Restart, and the script will use 12200 port’s data flow for parsing, and the protocol recognition is already in place.
Attached is the code written while translating, eyes already sore after writing this, mistakes are inevitable, you’re welcome to try it out.