Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-bugs: [Wireshark-bugs] [Bug 2591] New: FCP dissector doesn't correctly show response info flag.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 6 Jun 2008 18:24:06 -0700 (PDT)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2591

           Summary: FCP dissector doesn't correctly show response info flag.
           Product: Wireshark
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: joe@xxxxxxxxxxxxxxxx


Created an attachment (id=1858)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=1858)
patch to fix fcp respcode display.

Build Information:
wireshark 1.0.99 (SVN Rev 25425)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> 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 with GTK+ 2.12.1, with GLib 2.14.4, with libpcap 0.9.7, with libz
1.2.3, with POSIX capabilities (Linux), without libpcre, without SMI, without
ADNS, without Lua, with GnuTLS 1.6.3, with Gcrypt 1.2.4, without Kerberos,
without PortAudio, without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.

Running on Linux 2.6.23.9-85.fc8, with libpcap version 0.9.7.

Built using gcc 4.1.2 20070925 (Red Hat 4.1.2-33).

--
The Fibre-channel FCP dissector shows the wrong byte as the response info
response code byte.  The byte with offset 2 in the FCP frame is shown
instead of byte 3 inside the response info.

A patch is attached.


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

  • Follow-Ups:
    • [Wireshark-bugs] [Bug 2591] FCP dissector doesn't correctly show response info flag.
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 2588] Bad UTF-8 string from RSS dissector
  • Next by Date: [Wireshark-bugs] [Bug 2588] Bad UTF-8 string from RSS dissector
  • Previous by thread: [Wireshark-bugs] [Bug 2590] compilation failure on non-european windows ( due to non-ascii characters)
  • Next by thread: [Wireshark-bugs] [Bug 2591] FCP dissector doesn't correctly show response info flag.
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation