Wireshark-bugs: [Wireshark-bugs] [Bug 5124] Save As saves as incorrect file format when using "D
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 14 Jan 2012 02:10:52 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5124

Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
           Platform|x86-64                      |All
         Resolution|                            |FIXED
         OS/Version|Windows Server 2008         |All

--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx> 2012-01-14 02:10:52 PST ---
OK, there are several issues here:

1) That file is in a newer version of the NetMon 2.x/3.x file format, with
per-packet encapsulation, and Wireshark 1.4.x and 1.6.x don't support writing
out NetMon files with per-packet encapsulation, so it doesn't allow you to
write selected frames out in NetMon format.

2) For some reason, in some cases it was showing NetMon format even though it's
not supported.

3) In Wireshark 1.4.x and 1.6.x, the error messages shown if you try to save a
per-packet-encapsulation file in a format that doesn't support the
encapsulations of all the packets aren't as good as they should be, which is
probably why you got at least some of the strange errors.  What were the errors
and other strange behaviors you saw?

1) is fixed in the trunk.

I'm not sure what's causing 2), but even if I back out the fix for 1) from the
trunk, I'm not seeing it, so perhaps it was fixed by some other changes after
SVN revision 33881.

3) is also fixed in the trunk - it now reports that frame 1 has a frame type
that can't be saved in the specified file format if that's the case.  (There
really isn't anything better it can do in that case, and that case shouldn't
happen for NetMon files given the fix for 1).)

So I'll mark this as fixed.  I'm not sure the changes to fix it are safe to
backport, so I'll just leave them for the trunk (and thus for the automated
builds and development releases and for 1.8.0).

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