Wireshark-dev: Re: [Wireshark-dev] capture_file* in dissector code
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: mmann78@xxxxxxxxxxxx
Date: Wed, 13 Nov 2013 17:14:19 -0500 (EST)
A related question - Is packet_info->phdr == capture_file->phdr?   That would allow me to get the data I need always from packet_info* and not need the capture_file*
-----Original Message-----
From: Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Wed, Nov 13, 2013 3:39 pm
Subject: Re: [Wireshark-dev] capture_file* in dissector code

Hi,

On Wed, Nov 13, 2013 at 08:15:12AM -0500, mmann78@xxxxxxxxxxxx wrote:
> I was looking at making the "Decode As" functionality more generic, but my 
current solution involves having dissectors handle a callback function that 
passes in a capture_file* as an argument.  

I'm not sure if it's good enough, but epan_session->data in wireshark, tshark, 
rawshark points to capture_file *
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe