[bug-notifications] [wireshark 0002913]: wireshark no longer supports snoop capture format

Mantis Bug Tracker noreply at opencsw.org
Mon Jan 4 22:22:26 CET 2010


The following issue has been CLOSED 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=2913 
====================================================================== 
Reported By:                carlsonj
Assigned To:                hson
====================================================================== 
Project:                    wireshark
Issue ID:                   2913
Category:                   regular use
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-06-20 08:58 CEST
Last Modified:              2010-01-04 22:22 CET
====================================================================== 
Summary:                    wireshark no longer supports snoop capture format
Description: 
The latest version of wireshark in the CSW repository is:

  VERSION=1.0.0,REV=2008.06.11

... and it seems that it no longer understands snoop files.  I get
a pop-up box that says this:

  The file \"snoop.out\" isn\'t a capture file in a format
Wireshark
  understands.  (snoop: version 33554432 unsupported)

The file in format came directly from \"snoop -o\", and snoop
can read
it fine.  The \"file\" command identifies it as:

  snoop.out:      Snoop capture file - version 2

Downgrading to this previous version of wireshark fixes the problem:

  VERSION=1.0.0,REV=2008.04.02

====================================================================== 

---------------------------------------------------------------------- 
 (0007165) hson (manager) - 2010-01-04 22:22
 http://www.opencsw.org/mantis/view.php?id=2913#c7165 
---------------------------------------------------------------------- 
Fixed in 1.2.3,REV=2009.12.25




More information about the bug-notifications mailing list