 | 1 | initial version |
Can you talk about the size/scope/future of the dissector?
There are some good points to consider in here: Plugin for Telephony menu
Also do a search on "plugin" in the Wireshark Developer’s Guide. There is a line Submit dissectors as built-in whenever possible. but if you don't plan to share/contribute the code then doesn't matter.
There is also a line in doc/README.plugins that may apply:
(Note, however, that not all OSes on which Wireshark runs can support plugins.)
It's a pretty old comment (Note that not all OSes on which Ethereal runs can support plugins.) so not if this is still the case.
Back to the original question about size/scope, the Wireshark Lua API may not by highest performance but it's quick to develop in, doesn't require compiling/linking and can be a single source file you push to your end-user. Examples are available on the Wiki page - here and here.
| | 2 | No.2 Revision |
Can you talk about the size/scope/future of the dissector?
There are some good points to consider in here: Plugin for Telephony menu
Also do a search on "plugin" in the Wireshark Developer’s Guide. There is a line Submit dissectors as built-in whenever possible. but if you don't plan to share/contribute the code then doesn't matter.
There is also a line in doc/README.plugins that may apply:
(Note, however, that not all OSes on which Wireshark runs can support plugins.)
It's a pretty old comment (Note that not all OSes on which Ethereal runs can support plugins.) so not sure if this is still the case.
Back to the original question about size/scope, the Wireshark Lua API may not by highest performance but it's quick to develop in, doesn't require compiling/linking and can be a single source file you push to your end-user. Examples are available on the Wiki page - here and here.
| | 3 | No.3 Revision |
Can you talk about the size/scope/future of the dissector?
There are some good points to consider in here: Plugin for Telephony menu
Also do a search on "plugin" in the Wireshark Developer’s Guide. There is a line Submit dissectors as built-in whenever possible. but if you don't plan to share/contribute the code then doesn't matter.
There is also a line in doc/README.plugins that may apply:
(Note, however, that not all OSes on which Wireshark runs can support plugins.)
It's a pretty old comment (Note that not all OSes on which Ethereal runs can support plugins.) so not sure if this is still the case.
Back to the original question about size/scope, the Wireshark Lua API may not by highest performance but it's quick to develop in, doesn't require compiling/linking and can be a single source file you push to your end-user. Examples are available on the Wiki page - here and , here.
