Welcome to the kagwang wiki!
This is to introduce kagwang, answer the most urgent questions and point you to sources of further information.
kagwang is an extension to the Wireshark protocol analyzing software. It enables Wireshark to interprete IEEE 1905.1 protocol data. In Wireshark terminology, the process of interpreting a stream of data according to a certain protocol is called dissection. That's why, kagwang can be seen as an IEEE 1905.1 dissector for Wireshark.
For information on IEEE 1905.1 see IEEE Working Group, IEEE Standard Finder or Wikipedia.
Currently, the dissector supports only 1905.1 CMDUs, that is, Ethernet franes of type 0x893A. LLDP messages, which are of type 0x88CC, are not regarded at this stage. File a ticket to indicate that this feature would be helpful for you.
This dissector is for Wireshark users, who want to analyze and inspect IEEE 1905.1 protocol data. A major section of this community will be software developers, that write firmware for 1905.1-capable devices, who may want to test and debug exchanged traffic data.
First of all, you need a working Wireshark installation. Then, check out the source code from the code repository and read the readme file. Alternatively, you can download and unzip the package from the download section.
Copy the Lua script into the plugin directory of Wireshark. This is for
Start Wireshark and select the menu item "Internals | Supported Protocols". A list with supported protocols will appear. Check the list for an item "IEEE_1905.1" to verify the dissector installed correctly. The same line in that list gives a short description and version information of the dissector.
Alternatively, for temporary use of the dissector, you may load it by hand. Start Wireshark and select "Tools | Lua | Evaluate" from the menu. In the code pad that appears, type
:::lua
dofile("C:\\[path]\\1905.1.lua")
and press the "Evaluate" button. Afterwards, the IEEE 1905.1 should appear in the supported protocols list. Beware that with this method, the dissector is not installed permanently. It gets lost, when Wireshark is closed and has to be reloaded next time, when the software is started.
If you have questions, use the forum to either find a solution or ask your question. If, after trying all the above, you still need help, create a ticket or write an email to