ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 1693] NFSv4 "compound" frames show up as procedure "compou

Date: Tue, 11 Aug 2009 11:29:53 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1693





--- Comment #6 from Frank Schorr <fschorr@xxxxxxxxxxx>  2009-08-11 11:29:51 PDT ---
I/we am/are looking at revamping the NFS4 portion of the packet_nfs dissector
to make it usable in complex and large fileserver environments where network
captures that we analyze average >500MB a piece and can be as high as 8GB or
even larger.

The first area of focus will be to get SRT times for all the appropriate
"operations" as this is critical information when looking for specific protocol
bugs and performance issues.  The SRT information that is currently made
avalable from the RPC dissector is useless for any serious troubleshooting
because there is no granularity.

I'm looking to also understand what information needs to pulled up to lines in
both the packet list and packet details windows.  Some information is currently
pulled up to the packet list window but not enough in many troubleshooting
situations. Little if any information is pulled up is pulled up to the
"operations" lines in the packet detail window.

This is a long term project that is going to require a lot of additions and
changes.  Do we want to keep this bug report open to cover all the work or
should I open a new bug report for various stages along the way?

Thanks,

Frank


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