Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Richard van der Hoff <richardv@xxxxxxxxxxxxx>
Date: Fri, 02 Feb 2007 15:18:52 +0000

Richard van der Hoff wrote:
But my real question still stands: does the technique in README.developer section 2.7.2, with updating pinfo->desegment_offset and pinfo->desegment_len, not work?

Anybody know the answer to this?

If not, seems like there ought at least to be a caution in README.developer that it doesn't seem to work, following the principle that incorrect documentation is worse than no documentation.

Cheers

Richard


--
Richard van der Hoff <richardv@xxxxxxxxxxxxx>
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com

  • Follow-Ups:
    • Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?
      • From: Martin Mathieson
  • References:
    • Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?
      • From: Richard van der Hoff
  • Prev by Date: [Wireshark-dev] how to register the dissector
  • Next by Date: Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?
  • Previous by thread: Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?
  • Next by thread: Re: [Wireshark-dev] Multiple pdus atop TCP -- a lie in README.developer?
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation