Ask Your Question

Revision history [back]

DLT_USER mime_multipart: The multipart dissector could not find the required boundary parameter

Hi there!

We have a PCAPNG data packet with DLT_USER link-layer type. It contains the raw mime multipart message from boundary like: ----boundary Content-Type: ...

The custom DLT picks up the "mime_multipart" dissector, but wireshark says: "The multipart dissector could not find the required boundary parameter"

Looking at the code in packet-multipart.c -> dissect_multipart i can see, that if no previous "private_data", or "match_string" values are present in the "packet_info" structure, then this error is shown. (as it is/was a sub-dissector called from other protocols like HTTP,SIP,...) Question is, how can we use the "mime_multipart" dissector to dissect this message?

Previous question: https://ask.wireshark.org/question/31811/cant-get-a-dlt_user-type-to-be-dissected-as-mime-multipart/

Thanks, L.

DLT_USER mime_multipart: The multipart dissector could not find the required boundary parameter

Hi there!

We have a PCAPNG data packet with DLT_USER link-layer type. It contains the raw mime multipart message from boundary like:

----boundary

Content-Type: ......

The custom DLT picks up the "mime_multipart" dissector, but wireshark says: "The multipart dissector could not find the required boundary parameter"

Looking at the code in packet-multipart.c -> dissect_multipart i can see, that if no previous "private_data", or "match_string" values are present in the "packet_info" structure, then this error is shown. (as it is/was a sub-dissector called from other protocols like HTTP,SIP,...) Question is, how can we use the "mime_multipart" dissector to dissect this message?

Previous question: https://ask.wireshark.org/question/31811/cant-get-a-dlt_user-type-to-be-dissected-as-mime-multipart/

Thanks, L.

DLT_USER mime_multipart: The multipart dissector could not find the required boundary parameter

Hi there!

We have a PCAPNG data packet with DLT_USER link-layer type. It contains the raw mime multipart message from boundary like:

----boundary --boundary

Content-Type: application/json

...

The custom DLT picks up the "mime_multipart" dissector, but wireshark says: "The multipart dissector could not find the required boundary parameter"

Looking at the code in packet-multipart.c -> dissect_multipart i can see, that if no previous "private_data", or "match_string" values are present in the "packet_info" structure, then this error is shown. (as it is/was a sub-dissector called from other protocols like HTTP,SIP,...) Question is, how can we use the "mime_multipart" dissector to dissect this message?

Previous question: https://ask.wireshark.org/question/31811/cant-get-a-dlt_user-type-to-be-dissected-as-mime-multipart/

Thanks, L.