• News
  • Get Acquainted ▼
    • About
    • Download
    • Blog
  • Get Help ▼
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Issue Tracker
  • Develop ▼
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds
  • Project Host
  • SharkFest
Wireshark-bugs: [Wireshark-bugs] [Bug 11295] Incorrect interpretation of IPFIX flowEndSysUpTime,
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 23 Jun 2015 19:37:52 +0000

Comment # 7 on bug 11295 from Martin Mathieson
Why would you want to have more than one type of start/end pair in the same
flow?  
Regardless, an attempted fix is in https://code.wireshark.org/review/#/c/9063


You are receiving this mail because:
  • You are watching all bug changes.
  • References:
    • [Wireshark-bugs] [Bug 11295] New: Incorrect interpretation of IPFIX flowEndSysUpTime, flowStartSysUpTime fields when combined with other duration fields
      • From: bugzilla-daemon
  • Prev by Date: [Wireshark-bugs] [Bug 11029] can't install wireshark
  • Next by Date: [Wireshark-bugs] [Bug 9988] Unencrypted heartbeat requests are marked as encrypted
  • Previous by thread: [Wireshark-bugs] [Bug 11295] Incorrect interpretation of IPFIX flowEndSysUpTime, flowStartSysUpTime fields when combined with other duration fields
  • Next by thread: [Wireshark-bugs] [Bug 11295] Incorrect interpretation of IPFIX flowEndSysUpTime, flowStartSysUpTime fields when combined with other duration fields
  • Index(es):
    • Date
    • Thread
Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation Back to top