dissector_add("tcp.port", <portnumber>, protocol_handle);
It should be an example dissector in the README.developer that has this information.
/Tobias
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Martin Corraine (mcorrain)
Sent: den 11 juni 2008 16:45
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Ged125 protocol
Hello,
As someone told me, I should have my ged125 dissector be called by the TCP dissector. How do I go about doing this?
Thanks,
Martin
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Tuesday, June 10, 2008 6:11 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Ged125 protocol
On Jun 10, 2008, at 2:20 PM, Martin Corraine (mcorrain) wrote:
> My second question: Can I call the TCP dissector if the ged125 is
> based off of TCP?
"Based off of TCP" in what sense? If it runs over TCP, just as, for example, HTTP runs over TCP, the TCP dissector will call *your* dissector (or, as they'd say on Slashdot, "in Soviet Russia, TCP calls you!").
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev
