Wireshark · Wireshark-dev: Re: [Wireshark-dev] Bug in Wireshark Display filter engine caused by optimization of proto tree duri

[mmann78@xxxxxxxxxxxx]

Anders kind of beat me too it, but there are ways other than storing it in packet_info to exchange the data.  I don't know enough about the dissectors themselves to suggest the "best" way, but please don't consider packet_info as an option. 

 

 

 

-----Original Message-----
From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
Sent: Fri, Aug 21, 2015 10:38 am
Subject: Re: [Wireshark-dev] Bug in Wireshark Display filter engine caused by optimization of proto tree during dissect

Right, this would be a better approach if people are not
too
uncomfortable in storing this piece of info.

Thus, the radiotap (and
perhaps one other in the tree that seems to
know the channel frequency) could
store it as a value in the pinfo.

These changes would be much less intrusive in
the rest of the
infrastructure and confined to the ieee80211 series of
dissectors.

-- 
Regards,
Richard
Sharpe
(何以解憂？唯有杜康。--曹操)
___________________________________________________________________________
Sent
via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:   
https://www.wireshark.org/lists/wireshark-dev
Unsubscribe:
https://wireshark.org/mailman/options/wireshark-dev
            
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe