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: Wed, 1 Nov 2006 21:24:18 +0000 (GMT)

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





------- Comment #2 from stephentfisher@xxxxxxxxx  2006-11-01 21:24 GMT -------
Manual dissection looks like a proper TCP payload and saving the file in
Microsoft NetMon format and opening it in there shows a proper HTTP over TCP
over IP packet.  Do all of your packets show up malformed at the TCP level or
just this one?  The malformed warning is caused by the first attempt to get
data from the TCP payload - the source port - even though the packet is not
malformed at that packet.


-- 
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 1198] New: GTK+ 2.8 crashes while selecting text
  • Next by Date: [Wireshark-bugs] [Bug 301] Default storage location for traces on Windows is not Windows' encouraged practice
  • 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