Wireshark-dev: Re: [Wireshark-dev] Unexpected tap behaviour
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>
Date: Mon, 20 May 2013 15:35:17 -0400
On 05/20/2013 02:36 PM, Anders Broman wrote:

Hi,
I just implemented the export_pdu tap for Diameter as well as SIP to my
surprise if I don't define
a filter only SIP packets get experted from a file with both Diameter
and SIP. If I specify a filter of
"diameter or SIP" both gets exported. I would have expected both to be
exported with no filter. Could any one shed
some light on what's going on?
Diameter isn't queuing messages to the tap when !tree. Need to either lose this line in dissect_diameter_common(): 


   1082         if (!tree) return;


or move the tap queuing before it.