Wireshark · Wireshark-dev: Re: [Wireshark-dev] Best way to give configuration information to a protocol

[Michael Mann <mmann78@xxxxxxxxxxxx>]

I would agree that a dissector table for the GUIDs is probably the best way to go. I also just created a GUID dissector table in my recent work with Netmon.  grep "netmon.provider_id" for example of how to setup a GUID dissector table (it's much more straightforward than the DCE/RPC one)

 

 

-----Original Message-----
From: Pascal Quantin <pascal.quantin@xxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Mon, Sep 18, 2017 3:03 pm
Subject: Re: [Wireshark-dev] Best way to give configuration information to a protocol

Hi Juan Jose,

2017-09-18 17:12 GMT+02:00 Juan Jose Martin Carrascosa <juanjo@xxxxxxx>:

Hi all,

Which is the best way to pass configuration to a protocol? Do we have any builtin mechanisms? I tried to upload a patch using CSV at some point but it didn't succeed. So I wonder if there is any recommended way I can implement: table or list in the Preferences, XML file, CSV file...

My goal is to pass ("GUID", "plugin_name") pairs to the RTPS protocol so Wireshark knows dynamically what plugin it should call to deserialize data that is written by the DataWriter with id = "GUID". The GUID is part of the DATA packet and it is already dissected and known at that point.

A UAT dialog could be appropriate for your needs. Several dissectors are already using it and can be taken as an example (packet-ipsec.c, packet-http.c, ...).

Or if the GUID / plugin mapping never changes, you could create a dissector table and have your plugin register to this table (see register_dissector_table() / register_custom_dissector_table() and the corresponding dissector_add_XXX() functions).

Best regards,

Pascal.

___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe