On Tue, Aug 25, 2015 at 11:55 PM, Cody Doucette wrote:
>> I *think* (though I could easily be wrong), that the purpose of
>> declaring a field of type FT_PROTOCOL is for cases where one
>> protocol's dissector is about to invoke another protocol's dissector
>> for encapsulated data, and wants to s
> I *think* (though I could easily be wrong), that the purpose of
> declaring a field of type FT_PROTOCOL is for cases where one
> protocol's dissector is about to invoke another protocol's dissector
> for encapsulated data, and wants to show that encapsulated data of the
> other protocol as a fiel
w if your "subdissector" is truly its own protocol.
-Original Message-
From: Hadriel Kaplan
To: Developer support list for Wireshark
Sent: Fri, Aug 21, 2015 11:26 am
Subject: Re: [Wireshark-dev] use of FT_PROTOCOL
On Thu, Aug 20, 2015 at 5:17 PM, Cody Doucette wrote
On Thu, Aug 20, 2015 at 5:17 PM, Cody Doucette wrote:
> I am trying to extend the XIP dissector to include a sub-protocol that
> should only come after an XIP header. I want it displayed at the top-level
> in the "Packet Details" pane, so adding this protocol *inside* of the XIP
> dissector code s
I am trying to extend the XIP dissector to include a sub-protocol that
should only come after an XIP header. I want it displayed at the top-level
in the "Packet Details" pane, so adding this protocol *inside* of the XIP
dissector code seems like a good choice. I think FT_PROTOCOL will allow me
to d
