On Mon, Sep 3, 2018 at 11:32 AM David Aldrich
wrote:
> Our protocol includes a 16-bit field which is sub-divided into 4
> sub-fields. The width of those sub-fields is variable so I want to specify
> the widths using Wireshark preferences. I understand how to create and
> read Wireshark prefere
You might want to implement a function to handle this, something like so?
local function dissect_RuPortId_F(tree, buffer)
local t = {}
local mask = 2^my_protocol.prefs.ru_port_id_width - 1
local val = bit.band(buffer(4, 2):uint(), mask)
for i = 15, 0, -1 do
if bit.band(bi
On Tue, Sep 4, 2018 at 8:03 AM, Prashant Upadhyaya
wrote:
> Hi,
>
> Wireshark is seemingly not decoding the 'Reporting Triggers' IE properly.
> And then if further IE's are present, the whole packet is considered
> malformed.
>
> Version 2.6.2 (v2.6.2-0-g1b3cedbc)
>
> Example bytes of this IE for
Hi,
Wireshark is seemingly not decoding the 'Reporting Triggers' IE properly.
And then if further IE's are present, the whole packet is considered malformed.
Version 2.6.2 (v2.6.2-0-g1b3cedbc)
Example bytes of this IE for devs --
00 25 00 02 06 03
Regards
-Prashant
_
Hi Asaf,
master branch corresponds to the upcoming Wireshark 3.0 version (while all
the 2.6.x versions come from the master-2.6 branch). Based on
https://www.wireshark.org/lists/wireshark-dev/201802/msg00012.html it
should be out around November.
Best regards,
Pascal.
Le mar. 4 sept. 2018 à 13:4
Hi everyone,
Lately (prior release 2.6.3\2.6.2) i added dissector for the H.265/HEVC
protocol to the master branch.
I looked in the product cycle / road-map, but didn't find information.
Does anyone know when it's suppose to be release ?
Thank's
Asaf
___
