Wireshark-bugs: [Wireshark-bugs] [Bug 13213] New: RPC dissector doesn't match Replies to Calls w
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 06 Dec 2016 15:56:11 +0000
Bug ID 13213
Summary RPC dissector doesn't match Replies to Calls with RPC-over-RDMA transports
Product Wireshark
Version unspecified
Hardware All
OS All
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter chuck.lever@oracle.com 

Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-1656-gd3ac1a7)

Copyright 1998-2016 Gerald Combs <gerald@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.48.2, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, without
Lua, with GnuTLS 3.4.16, with Gcrypt 1.6.6, with MIT Kerberos, with GeoIP,
without nghttp2, without LZ4, without Snappy.

Running on Linux 4.8.10-200.fc24.x86_64, with Intel(R) Core(TM) i7-5557U CPU @
3.10GHz (with SSE4.2), with 1981 MB of physical memory, with locale
en_US.UTF-8,
with libpcap version 1.7.4, with GnuTLS 3.4.16, with Gcrypt 1.6.6, with zlib
1.2.8.

Built using gcc 6.2.1 20160916 (Red Hat 6.2.1-2).
--
This has been a problem for some time, I'm sorry I don't remember exactly where
it started.

Sample output:

   58   0.006610      LID: 11 → LID: 5       NFS 166 V3 FSINFO Call, FH:
0xd8d5771e
   59   0.006610       LID: 5 → LID: 11      InfiniBand 30 RC Acknowledge
QP=0x000224 
   60   0.006650       LID: 5 → LID: 11      RPC 134 V0 proc-0 Reply

"RPC V0 proc-0 Reply" means the RPC dissector was not able to find the matching
Call for this reply. RPC replies don't carry program/version/procedure
information. The dissector must find the matching Call in order to display
that, and then invoke the correct upper layer dissector (NFS, in this case).

You are receiving this mail because:
  • You are watching all bug changes.