Bug ID |
10253
|
Summary |
InfiniBand: incorrect mapping of fields
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.6
|
Hardware |
x86-64
|
OS |
Ubuntu
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 12866 [details]
PathRecord query request and response
Build Information:
wireshark 1.10.6 (v1.10.6 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
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 GTK+ 3.10.7, with Cairo 1.13.1, with Pango 1.36.1, with
GLib 2.39.91, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without
Python,
with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), with AirPcap.
Running on Linux 3.13.0-30-generic, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 2.12.23, Gcrypt 1.5.3, without AirPcap.
Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz
--
In this example, one machine has the GUID 0x1405000000027c and LID 49151
(0xBFFF).
The second machine has the GUID 0x14050000000080 and LID 10 (0x000A).
The second machine sends a PathRecord query to the Subnet Manager and the SM
replies.
As you can see in the attached picture, Wireshark maps the DGID and SGID
incorrectly.
The capture has been made with ibdump at the SM side, and wireshark is used for
the analysis.
You are receiving this mail because:
- You are watching all bug changes.