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 1271] rsync: "Follow TCP stream ..." is truncated

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


From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 3 Jan 2007 17:51:07 +0000 (GMT)

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





------- Comment #11 from toralf.foerster@xxxxxx  2007-01-03 17:51 GMT -------
Created an attachment (id=488)
 --> (http://bugs.wireshark.org/bugzilla/attachment.cgi?id=488&action=view)
pppoes packet

(In reply to comment #7)
One question: Wireshark reports now that the attached packet should have a
payload of 40, but b/c the "effective" payload is actually 12 (the remaining
packet is filled up with zeros). So should your patch respect this case too ?


-- 
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.

  • Prev by Date: [Wireshark-bugs] [Bug 1290] iuup parsing of rate control messages is incorrect
  • Next by Date: [Wireshark-bugs] [Bug 1290] iuup parsing of rate control messages is incorrect
  • Previous by thread: [Wireshark-bugs] [Bug 1271] rsync: "Follow TCP stream ..." is truncated
  • Next by thread: [Wireshark-bugs] [Bug 1271] rsync: "Follow TCP stream ..." is truncated
  • Index(es):
    • Date
    • Thread

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