Wireshark · Wireshark-dev: [Wireshark-dev] fragments and reassembly

Wireshark-dev: [Wireshark-dev] fragments and reassembly

Date: Wed, 29 Aug 2012 21:09:19 -0400 (EDT)

It appears that the reassembly API doesn't handle inserting "known middle" fragments (preferring them to be known consecutively). This appears to be at least one of the reasons the SCTP dissector does its own reassembly and why the new Bluetooth dissector from bug 7675 (https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7675) may need to do its own reassembly as well. Am I understanding the reassembly API correctly or am I just not being creative enough to understand how to represent a "known middle" fragment with the current API?

Follow-Ups:
- Re: [Wireshark-dev] fragments and reassembly
  - From: Mike Morrin

Prev by Date: Re: [Wireshark-dev] RFD: Creating subdirectories in epan/dissectors/
Next by Date: Re: [Wireshark-dev] RFD: Creating subdirectories in epan/dissectors/
Previous by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 44696: /trunk/ /trunk/epan/: packet.c packet.h /trunk/ui/gtk/: dissector_tables_dlg.c /trunk/: tshark.c
Next by thread: Re: [Wireshark-dev] fragments and reassembly
Index(es):
- Date
- Thread