| Bug ID | 
          9557
           | 
        
        
          | Summary | 
          Add support for dissecting GlueterFS/NFS file-handles
           | 
        
        
          | Classification | 
          Unclassified
           | 
        
        
          | Product | 
          Wireshark
           | 
        
        
          | Version | 
          unspecified
           | 
        
        
          | Hardware | 
          All
           | 
        
        
          | OS | 
          All
           | 
        
        
          | Status | 
          UNCONFIRMED
           | 
        
        
          | Severity | 
          Enhancement
           | 
        
        
          | Priority | 
          Low
           | 
        
        
          | Component | 
          Dissection engine (libwireshark)
           | 
        
        
          | Assignee | 
          [email protected]
           | 
        
        
          | Reporter | 
          [email protected]
           | 
        
        
          | Attachment #12299 Flags | 
          review_for_checkin?
           | 
        
      
        
        Created attachment 12299 [details]
Add support for dissecting Gluster/NFS file handles
Build Information:
master branch: TShark 1.11.3 (SVN Rev Unknown from unknown)
--
The nfs dissector has support for dissecting several types (depending on the
NFS-server) of file-handles. GlusterFS/NFS can not be dissected yet. It would
be helpful id Wireshark can display the components of the filehandle.
Example of the output with the attached patch:
    # ./tshark -r ~/dbench.pcap -V -Y "frame.number == 17960" \
      -X nfs.default_fhandle_type:GLUSTER 2>/dev/null | tail
    Network File System, FSSTAT Call DH: 0x593414b2
           [Program Version: 3]
        [V3 Procedure: FSSTAT (18)]
        object
            length: 36
            [hash (CRC-32): 0x593414b2]
            decode type as: GlusterFS/NFS file handle
            exportid: 4b4c81e7-8710-443e-8b14-e51b5ce2dedb
            gfid: 00000000-0000-0000-0000-000000000001
         
      
      
      You are receiving this mail because:
      
      
          - You are watching all bug changes.