Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 4831] Add '(read|write)_PDU_length' field in NFSv4 READ re

Date: Thu, 3 Jun 2010 06:57:36 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4831

--- Comment #4 from Cal Turney <turney_cal@xxxxxxx> 2010-06-03 06:57:35 PDT ---
(In reply to comment #3)
> Since this data is already in the tree:
> 
>         Opcode: WRITE (38)
>             stateid
>                 seqid: 0x00000000
>                 Data: 0f05a64a0100cf0e0000af01
>             offset: 32846
>             stable: UNSTABLE4 (0)
>             write_PDU_length: 47  <<< the new field
>             Data: <DATA>
>                 length: 47  <<<< the existing one
>                 contents: <DATA>
>                 fill bytes: opaque data
> 
> I suppose the real purpose here is to have a filterable field (the existing
> field is just a text item) and making the existing field filterable would be
> challenging since it's added by the RPC dissector.

That is exactly right.  My purpose was to provide a filterable field.  Since
the Data->length is not filterable and making it so would not be very
straight-forward, I decided to add a new field to the Read reply and Write
request tree.  Sound good?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.