Hi all,
Is there any way to specify the filter name using an API? Like, I use this
generic hf_field for my plugin and I specify the filter name in the code
paths.
It may not be the proper way to work when providing changes to the
community, but it would help a lot in my use case.
Thanks!
Juanjo
-Original Message-
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Guy Harris
Sent: den 6 februari 2016 20:10
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Reassembly of IP fragments gets confused by
multiple pa
On Feb 8, 2016, at 8:51 AM, Anders Broman wrote:
> It seems like there might not be a "solve all" solution to the cases listed,
> it also seems to me like there is a need for several flavors of "conversation"
> Such as the 5 tuple we have today for stuff like "decode as" and possibly
> other pr
On Feb 8, 2016, at 8:27 AM, Juan Jose Martin Carrascosa wrote:
> Is there any way to specify the filter name using an API? Like, I use this
> generic hf_field for my plugin and I specify the filter name in the code
> paths.
No.
You'll either have to create multiple fields (the preferred solut
Thanks for the info Guy.
I am not willing to hack the core, so I will go ahead with the multiple
fields.
Thanks,
Juanjo Martin
On Mon, Feb 8, 2016 at 6:21 PM, Guy Harris wrote:
> On Feb 8, 2016, at 8:27 AM, Juan Jose Martin Carrascosa
> wrote:
>
> > Is there any way to specify the filter name
Den 8 feb 2016 18:04 skrev "Guy Harris" :
>
> On Feb 8, 2016, at 8:51 AM, Anders Broman
wrote:
>
> > It seems like there might not be a "solve all" solution to the cases
listed, it also seems to me like there is a need for several flavors of
"conversation"
> > Such as the 5 tuple we have today for
On Feb 8, 2016, at 9:23 AM, Anders Broman wrote:
> Yes, when conversation is set up from say the SDP dissector for the upcoming
> rtp flow we will not know on which wire it will appear.
So perhaps the reassembly code should take into account the conversation ID
(with conversations not taking
Den 8 feb 2016 18:28 skrev "Guy Harris" :
>
> On Feb 8, 2016, at 9:23 AM, Anders Broman wrote:
>
> > Yes, when conversation is set up from say the SDP dissector for the
upcoming rtp flow we will not know on which wire it will appear.
>
> So perhaps the reassembly code should take into account the
