Wireshark will look for plugins at /usr/share/wireshark/plugins, according to the list of plugin directories at: B.2. Configuration Files and Folders
But that doesn't seem the case here, tested in Arch Linux and Ubuntu 14.04 with a LUA dissector. Adding the LUA dissector in the binary plugins dir (e.g. /usr/lib/wireshark/plugins/1.12.3 in my arch linux setup) works, though...
Any idea? What's the best way to provide custom LUA dissectors for wireshark in other packages?
asked 10 Feb '15, 05:16
The paths might be different on your system due to different compile time options for different Linux distributions. You will see the paths for your system in the Wireshark GUI.
With that information, please read the answer to the following question:
That should help to answer your question for your system.
Well, that depends how you want to distribute your Lua dissector. The most "consistent" way would be to provide an installation package (rpm, dpkg, etc.) for your traget dsitributions, including everything: Wireshark, tshark, your Lua code, etc. However that's going to create a lot of work if you want to make your Lua code available on a lot of platforms. So the best way depends totally on your requirements ;-)
answered 10 Feb '15, 05:49
Kurt Knochner ♦
I think the best way to distribute a Lua script is to have your users put the script into their Personal Plugins folder. The directory for this is not necessarily the same for all platforms everywhere - it's whatever is listed in
answered 12 Feb '15, 10:52