Wireshark improvements
From Linux NFS
(Difference between revisions)
| Line 3: | Line 3: | ||
server, but it could be better. Some examples: | server, but it could be better. Some examples: | ||
| - | * General maintenance, bug-fixing | + | * 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. | * 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. | ||
| - | * Update to 4.1. | + | * Update to 4.1. Garth Goodson has done some work at least on the pNFS parts. |
* (probably hard) 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. | ||
Revision as of 16:05, 2 March 2007
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
- 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.
- Update to 4.1. Garth Goodson has done some work at least on the pNFS parts.
- (probably hard) Given knowledge of the appropriate keys, decrypt and dissect privacy-encoded calls and replies.
