http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=44802
User: morriss
Date: 2012/09/06 07:10 PM
Log:
From Robert Bullen via https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7683 :
The reassembled fragments tree in the Packet Details view is awesome, but it
lacks one thing: a field that exposes the reassembled data.
tcp.data already exists for exposing a single TCP segment's payload as a byte
array. It would be handy to have something similar for a single application
layer PDU when TCP segment reassembly is involved. I propose
tcp.reassembled.data, named and placed after the already existing field
tcp.reassembled.length.
My primary use case for this feature is outputting tcp.reassembled.data with
tshark for further processing with a script.
The attached patch implements this very feature. Because the reassembled
fragment tree code is general purpose, i.e. not specific to just TCP, any
dissector that relies upon it can add a similar field very cheaply. In that
vein I've also implemented ip.reassembled.data and ipv6.reassembled.data, which
expose reassembled fragment data as a single byte stream for IPv4 and IPv6,
respectively. All other protocols that use the reassembly code have been left
alone, other than inserting NULL into their initializer lists for the newly
introduced struct field reassemble.h:fragment_items.hf_reassembled_data.
Directory: /trunk/epan/dissectors/
Changes Path Action
+23 -21 packet-6lowpan.c Modified
+2 -0 packet-atalk.c Modified
+2 -0 packet-bacapp.c Modified
+2 -0 packet-batadv.c Modified
+2 -0 packet-ber.c Modified
+2 -0 packet-btobex.c Modified
+3 -1 packet-capwap.c Modified
+2 -0 packet-cell_broadcast.c Modified
+2 -0 packet-clnp.c Modified
+2 -0 packet-dcerpc.c Modified
+2 -0 packet-dcm.c Modified
(54 files not shown)