Modbus/TCP hookup for subdissector

[Roland Knall <rknall () gmail com>]

Hello

As I need it for daily work, I have integrated subdissector code into
the Modbus/TCP dissector. Find the patch for this attached to
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5786


But here I have a question.

All the information I need for the subdissector is the actual payload
of the Modbus/TCP datastream. Additional information is not needed.
Therefore the dissector table get's registered on the id "mbtcp.data"
, and another dissector has to register to that table using the
keyword "data"

I have two questions about this process.

1. Is there a way to provide additional information to the
subdissector? Someone could use private_data, but that field I need
somewhere else, therefore can not be used here.
2. Should the table be registered in such a way? It seems rather
pointless, to just register using the keyword. A way, where you could
just register without providing sub information could be more useful,
as mbtcp.data says anyway for what you are registering.

kind regards,
Roland
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe