Wireshark-bugs: [Wireshark-bugs] [Bug 3055] use DESEGMENT_ONE_MORE_SEGMENT if there' s not enough bytes for computing the record length

From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 2 Dec 2008 22:59:01 -0800 (PST)

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3055





--- Comment #1 from Jaap Keuter <jaap.keuter@xxxxxxxxx>  2008-12-02 22:58:59 PDT ---
Why is DESEGMENT_ONE_MORE_SEGMENT the right value here? 
Reading from README.developer and in packet_info.h:
#define DESEGMENT_ONE_MORE_SEGMENT 0x0fffffff
#define DESEGMENT_UNTIL_FIN        0x0ffffffe
  guint32 desegment_len;        /* requested desegmentation additional length
                                   or
                                   DESEGMENT_ONE_MORE_SEGMENT:
                                     Desegment one more full segment
                                     (warning! only partially implemented)
                                   DESEGMENT_UNTIL_FIN:
                                     Desgment all data for this tcp session
                                     until the FIN segment.
So, if you can give the requested additional length that is the best option, to
lower overhead of trying to run the desegmentation for every byte received?


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.