I'm writing a dissector for an application that can use any tcp port
between 8000-8399. I've been doing multiple port dissection with the
following code, but it seems unmanageable for 400 ports.
local tcp_port_table = DissectorTable.get("tcp.port")
local mgi_dissector = tcp_port_table:get_dissecto
Hey folks,
I'm working on a new feature for Wireshark - to export IMF data as EML
filse. I was able to create the menu entries, the tap, and the output EML
files. But I'm having one issue: When I have the export objects dialog open
(by clicking on the newly-created "Export Objects -> IMF" menu) an
Le 1 nov. 2016 12:18, "Thomas Wiens" a écrit :
>
> On 01.11.2016 12:05, Pascal Quantin wrote:
>
> > Why not simply select the right function based on ft type? For
FT_(U)INT40
> > and above use the functions I indicated earlier.
>
> Now someone can use a value_string inside a bitmask field, even if
On 01.11.2016 12:05, Pascal Quantin wrote:
> Why not simply select the right function based on ft type? For FT_(U)INT40
> and above use the functions I indicated earlier.
Now someone can use a value_string inside a bitmask field, even if the
type FT_UINT64 is used.
If I change it so you have to u
Le 1 nov. 2016 11:47, "Thomas Wiens" a écrit :
>
> On 31.10.2016 17:02, Pascal Quantin wrote:
>
> > Looks like no one is currently working on it (or at least no patch is
> > queued in Gerrit yet). As you seem to be the fist user of those
functions
> > with 64bits fields, you are probably a good ca
On 31.10.2016 17:02, Pascal Quantin wrote:
> Looks like no one is currently working on it (or at least no patch is
> queued in Gerrit yet). As you seem to be the fist user of those functions
> with 64bits fields, you are probably a good candidate to submit a patch as
> you can easily test it ;)
>
