how can i add additional preferences for some protocols programmically?
how can i change the interface for some protocols programmically?
how can i change the interface for some protocols programmically?
OK, those are preferences, as the "Preferences" in the menu path should suggest.
What you need to do is to use the preferences API in Wireshark. The QUIC dissector isn't using the regular preferences API; see, for example, proto_register_smtp()
in epan/dissectors/packet-smtp.c
, and the calls to prefs_register_protocol()
and prefs_register_bool_preference()
in that routine.
See section 2.6 "User Preferences" of the doc/README.dissector
file in the source tree (or in the online Git repository).
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2019-03-05 16:46:50 +0000
Seen: 359 times
Last updated: Mar 07 '19
How to capture UDP traffic and not NBNS traffic?
No HTTP protocols in scan results
How to observe Message Session Relay Protocol packets
Seeking explanation on bytes count in 'Protocol hierarchy'
How to determine which processes are sending CLDAP Protocol to DST Port 389
captured two interfaces with dumpcap at 10Gbits/s
How to decode a protocol that wireshark doesn't recognize?
How is Packet List field highlighting enabled/disabled?
Your question is a bit vague and unclear, at least to me. Can you please elaborate?
For example, what do you mean by an "interface for some protocols"?
For example, with quic protocol, we just have one input field, but I need to extend this user interface with QT. Where can I find the source code for every dialog?@cmaynard, @Guy Harris.
I'm still not exactly sure what you're asking for, but I guess you're trying to add a new preference to the QUIC protocol dissector? Assuming so, you will need to modify the packet-quic.c file and then compile Wireshark. How you do that depends on what platform you're working on, but since you haven't indicated what that is, the best that I can do is to point you to the Wireshark Developer's Guide. Also have a look at the README.dissector file, and in particular section 2.6 of that file.
What do you mean by "input field"? Do you, as Chris Maynard suggests, mean a preference for the protocol?