http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=48491
User: guy
Date: 2013/03/22 04:59 PM
Log:
Don't wire into the reassembly code the notion that reassemblies should
be done on flows from one address to another; reassembly for protocols
running atop TCP should be done on flows from one TCP endpoint to
another.
We do this by:
adding "reassembly table" as a data structure;
associating hash tables for both in-progress reassemblies and
completed reassemblies with that data structure (currently, not
all reassemblies use the latter; they might keep completed
reassemblies in the first table);
having functions to create and destroy keys in that table;
offering standard routines for doing address-based and
address-and-port-based flow processing, so that dissectors not
needing their own specialized flow processing can just use them.
This fixes some mis-reassemblies of NIS YPSERV YPALL responses (where
the second YPALL response is processed as if it were a continuation of
a previous response between different endpoints, even though said
response is already reassembled), and also allows the DCE RPC-specific
stuff to be moved out of epan/reassembly.c into the DCE RPC dissector.
Directory: /trunk/epan/dissectors/
Changes Path Action
+7 -8 packet-6lowpan.c Modified
+5 -7 packet-atalk.c Modified
+8 -8 packet-bacapp.c Modified
+9 -12 packet-batadv.c Modified
+5 -7 packet-ber.c Modified
+13 -10 packet-btobex.c Modified
+7 -10 packet-capwap.c Modified
+5 -6 packet-cell_broadcast.c Modified
+6 -7 packet-clnp.c Modified
+134 -20 packet-dcerpc.c Modified
+6 -8 packet-dcm.c Modified
(71 files not shown)