http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1556
--- Comment #1 from Chaskiel Grundman <cg2v@xxxxxxxxxxxxxx> 2008-01-24 04:15:20 GMT ---
Created an attachment (id=1405)
--> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=1405)
patch to track afs "requests" by rx connection id
This problem seems to be caused by the way wireshark groups rx packets into
"requests" (all packets in a single rpc and its reply are part of the same
"request"). Wireshark currently uses the udp endpoints, the rx service id, and
the call number. This is incorrect, since call numbers may be (and will be)
re-used in different rx connections between the same peers on the same service.
The correct way to group the packets is (optionally) by endpoint, then
epoch/connection id (cid), and call number.
The attached patch replaces the service id check with one that uses the epoch
and cid, and exports the epoch and cid values from the rx dissector to the afs
dissector. With this patch applied, the testcase from redhat is correctly
handled.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.