Wireshark improvements

From Linux NFS

(Difference between revisions)
Jump to: navigation, search
 
(6 intermediate revisions not shown)
Line 1: Line 1:
[http://www.wireshark.org/ Wireshark] (previously known as Ethereal) is
[http://www.wireshark.org/ Wireshark] (previously known as Ethereal) is
invaluable for understanding what's happening on the wire between a client and
invaluable for understanding what's happening on the wire between a client and
-
server.  Some todo's:
+
server, but it could be better.  Some examples:
-
* General maintenance, bug-fixing: e.g. last I checked it was mis-parsing NFSv4 setattr ops.
+
* General maintenance, bug-fixing
-
* At least if it sees the setclientid call (which includes the address, port, and protocol to use for callbacks), wireshark should be able to properly display operations on the callback channel.  Currently it doesn't.
+
* Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
-
* (probably hard) Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
+
* parse EXCHANGE_ID flags
 +
* Spurious unparsed data at end of RECLAIM_COMPLETE request/reply?
 +
* Fix parsing of fs_layout_type?  (Getting unhelpful parsing of zero-length array, spurious "Malformed Packet: NFS".)
 +
* Fix list of compound ops in packet-list pane (currently tends to include lots of spurious test-stateid's for some reason).
 +
* Handle open delegation WANT_ flags.
 +
 
 +
Is all of this done now?:
 +
 
 +
* callback channel decoding: in 4.1 case, this is easy.  In 4.0 case, requires seeing the setclientid call.
 +
* Update to 4.1.  (Mostly done:  may still be some odds an ends missing, though.
 +
* Add decoders for rpcbind protocol versions 3 and 4.  (Done or not?)
 +
* Test to make sure all existing NFS and RPC related decoders work nicely with IPv6. (?)

Latest revision as of 20:42, 20 October 2010

Wireshark (previously known as Ethereal) is invaluable for understanding what's happening on the wire between a client and server, but it could be better. Some examples:

  • General maintenance, bug-fixing
  • Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
  • parse EXCHANGE_ID flags
  • Spurious unparsed data at end of RECLAIM_COMPLETE request/reply?
  • Fix parsing of fs_layout_type? (Getting unhelpful parsing of zero-length array, spurious "Malformed Packet: NFS".)
  • Fix list of compound ops in packet-list pane (currently tends to include lots of spurious test-stateid's for some reason).
  • Handle open delegation WANT_ flags.

Is all of this done now?:

  • callback channel decoding: in 4.1 case, this is easy. In 4.0 case, requires seeing the setclientid call.
  • Update to 4.1. (Mostly done: may still be some odds an ends missing, though.
  • Add decoders for rpcbind protocol versions 3 and 4. (Done or not?)
  • Test to make sure all existing NFS and RPC related decoders work nicely with IPv6. (?)
Retrieved from "http://wiki.linux-nfs.org/wiki/index.php/Wireshark_improvements"
Personal tools