Ethereal-dev: Re: [Ethereal-dev] Re: pinfo->can_desegment Handling (was [Ethereal-cvs] rev 160

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
Date: Wed, 5 Oct 2005 11:22:42 +1000
You should not use these fields directly.

Use tcp_dissect_pdus() and that function will handle everything for you.
There are plenty of examples on how to use tcp_dissect_pdus, just grep for it in epan/dissectors



On 10/5/05, Mike Duigou <ethereal@xxxxxxxxxx> wrote:
Any chance of a more complete explanation of how dissectors should use
the can_desegment pinfo field for README.developer perhaps? Handling for
this field currently gets no mention in any of the README files.

I've read the description in packet_info.h but am still unsure of what
my dissector should do.

Mike

guy@xxxxxxxxxxxx wrote:
> User: guy
> Date: 2005/10/03 08:16 PM
>
>  Set "pinfo->can_desegment" before calling dissectors; that's expected
>  for dissectors that do TCP-style desegmentation.

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev