https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6462
Summary: Added v4 error status to packet detail window.
Product: Wireshark
Version: 1.6.2
Platform: Other
OS/Version: All
Status: NEW
Severity: Major
Priority: Low
Component: Wireshark
AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
ReportedBy: steved@xxxxxxxxxx
Created an attachment (id=7253)
--> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=7253)
The patch that adds v4 status
Build Information:
Version 1.6.2
Copyright 1998-2011 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 (64-bit) with GTK+ 2.24.4, with GLib 2.28.8, with libpcap 1.1.1, with
libz 1.2.5, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8,
without c-ares, without ADNS, with Lua 5.1, with Python, with GnuTLS 2.10.5,
with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel
(built May 5 2011 11:00:51), with AirPcap.
Running on Linux 3.1.0-0.rc9.git0.0.fc16.x86_64, with libpcap version 1.1.1,
with libz 1.2.5, GnuTLS 2.12.7, Gcrypt 1.5.0, without AirPcap.
Built using gcc 4.6.0 20110603 (Red Hat 4.6.0-10).
--
Here are a couple tweaks to the NFSv4 dissectors
that will show all the ops and their status on in the
packet detail window. Showing all the ops in that
window I think works well the new configuration
of only showing 'significant' v4 opts in the packet
list window. Plus there is plenty of real estate
on that line.
I also put NFS4_OP_SEQUENCE on the same tier as NFS4_OP_PUTFH
since when NFSv4.1 is used, the SEQUENCE will in every
compound like PUTFHs are.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
