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-bugs: [Wireshark-bugs] [Bug 1197] IP packet display with Protocol "TCP"

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


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 3 Nov 2006 22:18:53 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1197





------- Comment #9 from stephentfisher@xxxxxxxxx  2006-11-03 22:18 GMT -------
The malformed packets really are malformed - the PPPoE payload length is not
reported properly.  For example, in the http stream packet #37 reports a length
of 15 whereas it should be reporting that 271 bytes remain in the packet.  The
packets may show up as TCP or IP but not be filterable because the payload
length is so short that the packets are cut off in the dissector.  This does
not appear to be a Wireshark issue.


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

  • References:
    • [Wireshark-bugs] [Bug 1197] New: IP packet display with Protocol "TCP"
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 1197] IP packet display with Protocol "TCP"
  • Next by Date: [Wireshark-bugs] [Bug 1200] Wireshark hangs while opening a particular capture file
  • Previous by thread: [Wireshark-bugs] [Bug 1197] IP packet display with Protocol "TCP"
  • Next by thread: [Wireshark-bugs] [Bug 1197] IP packet display with Protocol "TCP"
  • Index(es):
    • Date
    • Thread

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