Bug ID |
11363
|
Summary |
IB: Create single conversation for Infiniband connections whenever possible
|
Product |
Wireshark
|
Version |
Git
|
Hardware |
x86-64
|
OS |
Red Hat
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 13733 [details]
NFS V4 RDMA mount
Build Information:
Wireshark 1.99.6 (v1.99.6rc0-312-g8be710c from unknown)
Copyright 1998-2015 Gerald Combs <[email protected]> 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 Qt 4.8.5, with libpcap, with POSIX capabilities (Linux),
with libnl 1, with libz 1.2.7, with GLib 2.36.3, without SMI, without c-ares,
without ADNS, without Lua, with GnuTLS 3.1.18, with Gcrypt 1.5.3, with MIT
Kerberos, without GeoIP, without PortAudio, without AirPcap.
Running on Linux 3.10.0-123.el7.x86_64, with locale C, with libpcap version
1.5.3, with libz 1.2.7, with GnuTLS 3.1.18, with Gcrypt 1.5.3.
Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (with SSE4.2)
Built using gcc 4.8.2 20140120 (Red Hat 4.8.2-16).
--
IB packets do not have source QP in each packet. For that reason
conversations created by infiniband dissector create one conversation
for each direction of the connection. This does not allow dissectors
above IB to be able to fully analyse the protocol such as matching
requests to responses. This behavior can be improved if our capture
includes CM establishment packets that contain both source and
destination QP numbers.
Moreover, protocols, like RPC - that dissect the replay's fully based on the
request - can't dissect the replay.
You are receiving this mail because:
- You are watching all bug changes.