https://github.com/Cisco-Talos/Winbox_Protocol_Dissector

https://github.com/Cisco-Talos/Winbox_Protocol_Dissector

Last synced: 15 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/Cisco-Talos/Winbox_Protocol_Dissector
• Owner: Cisco-Talos
• License: bsd-3-clause
• Created: 2018-09-19T16:50:57.000Z (about 6 years ago)
• Default Branch: master
• Last Pushed: 2018-09-24T19:04:07.000Z (about 6 years ago)
• Last Synced: 2024-07-31T14:09:29.002Z (4 months ago)
• Language: Lua
• Size: 267 KB
• Stars: 71
• Watchers: 13
• Forks: 20
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Mikrotik Winbox Protocol Dissector for Wireshark

*Note: This only works on "non-secure" sessions as specified by the client*

---

## Installation is Simple

* LUA-based dissector, no recompilation necessary

* Drop the `Winbox_Dissector.lua` file into your `/$HOME/.wireshark/plugins` folder.

---

## Usage

By default, any TCP traffic to/from TCP port 8291 will be decoded as Winbox traffic once the dissector is installed.

While a single message from the client/server to its destination would be preferable for

parsing purposes. This is not always the case, observing live communications proved that

there are many ways that Winbox Messages can be formatted and sent.

Below is an example of a Winbox communications capture that has the following properties:

* Multiple messages sent in the same packet.

* Messages containing 1 or more 2-byte "chunks" that need removal before parsing

* Messages too long for a single packet -- TCP reassembly applied.

* Messages containing additional "nested" messages

### Without Dissector Installed

![alt text](https://github.com/Cisco-Talos/Winbox_Protocol_Dissector/blob/master/images/before-dissection.png "Without Dissector Installed")

### With Dissector Installed

![alt text](https://github.com/Cisco-Talos/Winbox_Protocol_Dissector/blob/master/images/dissected.png "With Dissector Installed")