[Wireshark-bugs] [Bug 15484] New: Buildbot crash output: fuzz-2019-02-05-18929.pcap

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15484

Bug ID: 15484
   Summary: Buildbot crash output: fuzz-2019-02-05-18929.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
OS: Ubuntu
Status: CONFIRMED
  Severity: Major
  Priority: High
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: buildbot-do-not-re...@wireshark.org
  Target Milestone: ---

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2019-02-05-18929.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/16787-geonw.pcap

Build host information:
Linux wsbb04 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic

Buildbot information:
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=5000
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_GOT_REVISION=53b55bfb5f775dad6c434bb5b18e260d79b0104d

Return value:  0

Dissector bug:  0

Valgrind error count:  5



Git commit
commit 53b55bfb5f775dad6c434bb5b18e260d79b0104d
Author: Peter Wu 
Date:   Tue Feb 5 13:40:23 2019 +0100

editcap: warn when --inject-secrets is given a RSA private key

While the documentation of "editcap --inject-secrets" mentions support
for key log files only, people might misinterpret that and assume
support for RSA private keys. This is explicitly not supported due to
the sensitivity of these files. In order to be helpful, print a warning.

Change-Id: Ia7b464c17f1dfb550729dd35775290ed28e14510
Reviewed-on: https://code.wireshark.org/review/31893
Petri-Dish: Peter Wu 
Tested-by: Petri Dish Buildbot
Reviewed-by: Peter Wu 


Command and args: ./tools/valgrind-wireshark.sh -b
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin
 
==25830== Memcheck, a memory error detector
==25830== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==25830== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==25830== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2019-02-05-18929.pcap
==25830== 
==25830== Conditional jump or move depends on uninitialised value(s)
==25830==at 0x6F2B127: dissect_geonw (packet-geonw.c:2468)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x8177097: dissector_try_uint_new (packet.c:1383)
==25830==by 0x81773CB: dissector_try_uint (packet.c:1407)
==25830==by 0x6EBCB6E: dissect_ethertype (packet-ethertype.c:261)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x817A252: call_dissector_only (packet.c:3141)
==25830==by 0x8175CD4: call_dissector_with_data (packet.c:3154)
==25830==by 0x6EBBE7C: dissect_eth_common (packet-eth.c:527)
==25830==by 0x6EBA76A: dissect_eth (packet-eth.c:803)
==25830== 
==25830== Conditional jump or move depends on uninitialised value(s)
==25830==at 0x6F2B166: dissect_geonw (packet-geonw.c:2501)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x8177097: dissector_try_uint_new (packet.c:1383)
==25830==by 0x81773CB: dissector_try_uint (packet.c:1407)
==25830==by 0x6EBCB6E: dissect_ethertype (packet-ethertype.c:261)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x817A252: call_dissector_only (packet.c:3141)
==25830==by 0x8175CD4: call_dissector_with_data (packet.c:3154)
==25830==by 0x6EBBE7C: dissect_eth_common (packet-eth.c:527)
==25830==by 0x6EBA76A: dissect_eth (packet-eth.c:803)
==25830== 
==25830== Conditional jump or move depends on uninitialised value(s)
==25830==at 0x6F2B187: dissect_geonw (packet-geonw.c:2501)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x8177097: dissector_try_uint_new (packet.c:1383)
==25830==by 0x81773CB: dissector_try_uint (packet.c:1407)
==25830==by 0x6EBCB6E: dissect_ethertype (packet-ethertype.c:261)
==25830==by 0x817B5B7: call_dissector_through_handle (packet.c:706)
==25830==by 0x8177289: call_dissector_work (packet.c:791)
==25830==by 0x817A252: call_dissector_only (packet.c:3141)
==25830==by 

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #12 from Christopher Maynard  ---
(In reply to Guy Harris from comment #10)
> For programs that put long help summaries, we might want to do it GNU-style:

That was basically what I had in mind for "--version".

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #11 from Christopher Maynard  ---
(In reply to Guy Harris from comment #8)
> There's "what do they document in the help output" and "what do they
> implement".  The whole point of this bug is to report that they differ,
> right?

That was the original intent yes, to point out that there are undocumented
version options (whether "-V", "-v" or even "--version" as I had omitted that
variant), and also in some cases "-h" itself is missing.

But apart from some missing documented options, I also pointed out that we do
have an inconsistency with respect to the version options ("-v" or "-V"), so we
can either leave them as they are, which is probably confusing, or try to make
the option consistent across all the tools.  If you'd prefer that be filed as a
separate bug report, then I can file that tomorrow?

Lastly, if we'd like to also support "--version" for all tools that are
currently missing it (dftest, idl2wrs, lemon, mmdbresolve, randpkt, sharkd),
then I suppose that could also be filed as a separate bug as well?

(In reply to Guy Harris from comment #9)
> ...but adding --verbose as well might help here.  Unlike --version, that
> would be new, so we'd have to wait a while for the versions that don't
> support --verbose to be rare enough that we can expect people to be able to
> convert their scripts to use --verbose.  (And we should probably tell them
> to do so.)

Sorry, this part wasn't completely clear to me.  Which tools currently support
"--verbose"?  And are you suggesting we use "--verbose" instead of "--version"?
 That seems a little unintuitive to me for returning the version of the tool,
unless you're suggesting that because we currently return more information than
simply the version in the "-v" (or "-V") output that it's actually more
applicable?  In that case, would "-v" (or "-V") be changed to *only* return the
version?  For example:

mergecap --version
Mergecap (Wireshark) 3.1.0 (v3.1.0rc0-8-g53b55bfb)

... whereas we'd introduce --versbose to return what "-v" ("-V") returns now?:

mergecap --verbose
Mergecap (Wireshark) 3.1.0 (v3.1.0rc0-8-g53b55bfb)

Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GLib 2.52.2, with zlib 1.2.11.

Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Xeon(R) CPU
E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with
locale C, binary plugins supported (0 loaded).

Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730).

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #10 from Guy Harris  ---
(In reply to Christopher Maynard from comment #7)
> (In reply to Guy Harris from comment #6)
> > All the programs that currently support a version option support --version
> > in addition to one of -v/-V.
> 
> It would seem that none of the tools document --version in the -h output
> though.

We don't tend to document any long versions that have corresponding short
versions.

For programs that put long help summaries, we might want to do it GNU-style:

$ grep --help   
Usage: grep [OPTION]... PATTERN [FILE]...
Search for PATTERN in each FILE or standard input.
PATTERN is, by default, a basic regular expression (BRE).
Example: grep -i 'hello world' menu.h main.c

Regexp selection and interpretation:
  -E, --extended-regexp PATTERN is an extended regular expression (ERE)
  -F, --fixed-strings   PATTERN is a set of newline-separated strings
  -G, --basic-regexpPATTERN is a basic regular expression (BRE)
  -P, --perl-regexp PATTERN is a Perl regular expression
  -e, --regexp=PATTERN  use PATTERN for matching
  -f, --file=FILE   obtain PATTERN from FILE
  -i, --ignore-case ignore case distinctions
  -w, --word-regexp force PATTERN to match only whole words
  -x, --line-regexp force PATTERN to match only whole lines
  -z, --null-data   a data line ends in 0 byte, not newline

although I might do

  -f FILE, --file FILE  obtain PATTERN from FILE

to make it a bit clearer.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #9 from Guy Harris  ---
(In reply to Guy Harris from comment #6)
> (In reply to Christopher Maynard from comment #5)
> > (In reply to Guy Harris from comment #1)
> > > Eliminating the inconsistency without potentially breaking some user 
> > > habits
> > > and scripts is impossible; I suspect 2) would be less painful than 1).
> > 
> > Would the introduction of "--version" to all tools help here?  Give folks
> > time to adjust and modify scripts to convert from either "-v" or "-V" to
> > "--version" before a change is made?
> 
> That's one reason why I added --version.  (I think it's also a common GNU
> convention, which is another reason.)
> 
> All the programs that currently support a version option support --version
> in addition to one of -v/-V.

...but adding --verbose as well might help here.  Unlike --version, that would
be new, so we'd have to wait a while for the versions that don't support
--verbose to be rare enough that we can expect people to be able to convert
their scripts to use --verbose.  (And we should probably tell them to do so.)

Given the "enterprise" deployments of some Linux distributions, which can be
slw to update to newer versions, we might have to wait a while for the
last "no --verbose" version to disappear

(Does any version of CentOS ship Wireshark 2.x, for any value of x?)

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #8 from Guy Harris  ---
(In reply to Christopher Maynard from comment #7)
> (In reply to Guy Harris from comment #6)
> > All the programs that currently support a version option support --version
> > in addition to one of -v/-V.
> 
> It would seem that none of the tools document --version in the -h output
> though.

There's "what do they document in the help output" and "what do they
implement".  The whole point of this bug is to report that they differ, right?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #7 from Christopher Maynard  ---
(In reply to Guy Harris from comment #6)
> All the programs that currently support a version option support --version
> in addition to one of -v/-V.

It would seem that none of the tools document --version in the -h output
though.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14306] Export time shift packets into new pcapng file.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14306

Guy Harris  changed:

   What|Removed |Added

 Status|RESOLVED|CONFIRMED
 Resolution|FIXED   |---

--- Comment #9 from Guy Harris  ---
(In reply to Christopher Maynard from comment #7)
> (In reply to Gerrit Code Review from comment #4)
> > Change 31057 had a related patch set uploaded by Michael Mann:
> > TimeShiftDialog should be considered an "edit" operation
> > 
> > https://code.wireshark.org/review/31057
> 
> There's a lengthy discussion about use cases in comment 6, but that aside,
> doesn't this patch resolve this bug?

Only if, when you shift time stamps and save, the saved packets have their time
stamps shifted in the file.  And...

...they don't.

That's why that change did Ping-Bug: it was necessary, but *not* sufficient, to
cause shifted time stamps to be saved.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #6 from Guy Harris  ---
(In reply to Christopher Maynard from comment #5)
> (In reply to Guy Harris from comment #1)
> > Eliminating the inconsistency without potentially breaking some user habits
> > and scripts is impossible; I suspect 2) would be less painful than 1).
> 
> Would the introduction of "--version" to all tools help here?  Give folks
> time to adjust and modify scripts to convert from either "-v" or "-V" to
> "--version" before a change is made?

That's one reason why I added --version.  (I think it's also a common GNU
convention, which is another reason.)

All the programs that currently support a version option support --version in
addition to one of -v/-V.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12350] OS/application option from IDB isn't shown in Capture File Properties (a.k.a. Summary)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12350

--- Comment #4 from Guy Harris  ---
(In reply to Jasper Bongertz from comment #0)
> The OS / capture application information options has been moved from the SHB
> to the IDB for PCAPng files in 2.1.x.

Moved?

Both the SHB and IDB support the OS option; shouldn't we set, and display,
both, if available?

(If you're capturing on a remote interface using rpcap or a remote-capture
extcap program, you should only have those fields in the IDB if you know the OS
and application running on the *remote* machine; to quote the current pcapng
spec:

  if_os:

The if_os option is a UTF-8 string containing the name of the operating
system of the machine in which this interface is installed. This can be
different from the same information that can be contained by the Section Header
Block (Section 4.1) because the capture can have been done on a remote machine.

There *is* no capture application option for the IDB.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #5 from Christopher Maynard  ---
(In reply to Guy Harris from comment #1)
> Eliminating the inconsistency without potentially breaking some user habits
> and scripts is impossible; I suspect 2) would be less painful than 1).

Would the introduction of "--version" to all tools help here?  Give folks time
to adjust and modify scripts to convert from either "-v" or "-V" to "--version"
before a change is made?

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14284] Horrible slow/sluggish UI in High Sierra (macOS 10.13)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14284

--- Comment #16 from Guy Harris  ---
(In reply to Alexis La Goutte from comment #13)
> Can you try last 2.9 nighty build ?

I just tested with somewhat recent master-2.4 and master-2.6 builds and a
*very* recent master-3.0 build, with all the BPF devices changed to be
root-only.

I saw sluggishness when typing into the packet filter field with the 2.4 and
2.6 builds, but not with the 3.0 build.  The sluggishness went away when I gave
the access_bpf group access to the BPF devices, so I think that's the
sluggishness caused by making the BPF devices inaccessible.

So this appears to be fixed in 3.0.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11807] Round Trip Time Graph is blank initially.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11807

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> Wireshark 2.0 is no longer supported as of November 18, 2017.  Does this
> problem still exist with the latest stable version of Wireshark or with
> master?  If it does, please provide full Wireshark version information from
> "About -> Wireshark" (or "tshark -v" output).

Since there's been no additional feedback, I'm closing the bug.  If the problem
can be reproduced using the latest stable version of Wireshark, then feel free
to reopen the bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12067] Unable to resize the packet list pane, packet details pane

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12067

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #20 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #19)
> Is there any update on this bug?  Wireshark 2.0.x is end of life as of
> November 18, 2017 and Wireshark 2.2.x is end of life as of September 7,
> 2018.  Does the bug still exist even with the latest stable version of
> Wireshark?  If so, please provide updated build and other relevant
> information.

There hasn't been any additional feedback, so I'm going to close this bug.  If
the problem can be reproduced using the lates stable version of Wireshark, then
feel free to reopen the bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12035] Qt Wireshark hangs when stopping the capture

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12035

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #12 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #11)
> (In reply to Florian from comment #10)
> > 2.4.1 on Windows 10 still has the same issue, so I don't think it's a
> > duplicate :)
> 
> Is this bug still applicable with the latest stable version of Wireshark,
> currently 2.6.6?  (I can't reproduce this problem myself.)

Since there's been no feedback and the bug can't be reproduced with version
2.6.6, I'm going to close the bug.  If it can still be reproduced by someone
else using the latest stable version of Wireshark, then feel free to reopen the
bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12350] OS/application option from IDB isn't shown in Capture File Properties (a.k.a. Summary)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12350

Christopher Maynard  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> I believe this is fixed now, as the information is showing up under both the
> "Statistics -> Capture File Properties" as well as in capinfos output when
> tested with both Wireshark 2.6.6 and master on Windows 10.
> 
> Please confirm so the bug can be closed.

I'm going to assume the bug was fixed and close it.

(In reply to Christopher Maynard from comment #2)
> Or is the bug that capture files captured prior to the change don't show the
> OS and application information with post 2.1.x changes?  My tests above were
> with a capture file using 2.6.6 and master, not with one taken with say,
> 2.0.x.

And I'm going to assume that this wasn't the case.

If either of my assumptions are wrong and the bug can still be reproduced using
the latest stable version of Wireshark, then feel free to reopen the bug and
update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12111] Unable to open without error DBusMenuExporterPrivate

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12111

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #3 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #2)
> (In reply to Balint Reczey from comment #1)
> > Seems to be a bug in Qt, not GTK UI.
> 
> Is this bug still applicable with the latest stable version of Wireshark
> (and updated Qt)?  Wireshark 2.0.x is no longer supported as of November 18,
> 2017 and Qt 5.2.1 is quite old.

No feedback so I'm assuming this bug is no longer applicable.  If the bug can
be reproduced using the latest stable version of Wireshark, then feel free to
reopen the bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12148] Unable to open two Wireshark instances simultaneously

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12148

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #2)
> Please update to the latest stable version and confirm that this problem is
> resolved.  Without feedback, I'll assume the problem is fixed and close the
> bug soon.

No feedback so I'm closing the bug.  If it can be reproduced using the latest
stable version of Wireshark, then feel free to reopen the bug and update the
relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #4 from Christopher Maynard  ---
(In reply to Guy Harris from comment #3)
> At least in a recent build from the master branch:
> 
> $ build/run/captype -h

Yes, but other tools show:

-h   display this help and exit


> $ build/run/captype -v

Agreed, it belongs in the category that doesn't list it in the -h output.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13184] Access violation in Wireshark!rescan_packets+0x345

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13184

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #9 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #8)
> A lot has changed since the 2+ years this bug has been filed and Wireshark
> 2.2.x is no longer supported as of September 7, 2018.  Can this bug still be
> reproduced with the latest stable version of Wireshark?

No feedback, so I'm assuming the bug is no longer applicable and will close it.
 If the problem can be reproduced with the latest stable version of Wireshark,
then feel free to reopen the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #3 from Guy Harris  ---
(In reply to Christopher Maynard from comment #0)
> The following tools don't implement either a version or help option
> 1) captype

At least in a recent build from the master branch:

$ build/run/captype -h
Captype (Wireshark) 2.9.1 (v2.9.1rc0-614-g73183542)
Print the file types of capture files.
See https://www.wireshark.org for more information.

Usage: captype  ...

$ build/run/captype -v
Captype (Wireshark) 2.9.1 (v2.9.1rc0-614-g73183542)

Copyright 1998-2019 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GLib 2.37.6, with zlib 1.2.11.

Running on Mac OS X 10.13.6, build 17G4015 (Darwin 17.7.0), with Intel(R)
Core(TM) i7-4980HQ CPU @ 2.80GHz (with SSE4.2), with 16384 MB of physical
memory, with locale en_US.UTF-8, with zlib 1.2.11, binary plugins supported (0
loaded).

Built using clang 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.11.45.5).

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13293] RTP Streams: Wireshark crashes

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13293

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|INCOMPLETE  |RESOLVED

--- Comment #14 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #13)
> Wireshark 2.2.x is no longer supported as of September 7, 2018.  Can you
> retest
> with the latest stable version of Wireshark and update the bug report with
> your
> findings?

Since there's been no feedback, I assume there is no crash problem with the
latest stable version of Wireshark and I'm closing the bug.  If the problem can
be reproduced, then feel free to reopen the bug and update the relevant
information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #2 from Guy Harris  ---
(In reply to Christopher Maynard from comment #0)
> I suppose there's nothing to be done with either lemon or mmdbresolve. 

lemon isn't our program; we could add "-v" in addition to "-x" to print the
version as a patch, and try to convince the maintainers to adopt that (so that
they don't add their own -v flag to do something else).

mmdbresolve *is* our program, so we don't have to deal with upstream to add
that option.  I'm not sure we'd *need* to use GLib (which is either
LGPL-licensed or GPL-licensed, which might cause a licensing issue) to add it.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

Guy Harris  changed:

   What|Removed |Added

   Hardware|x86-64  |All
 OS|Windows 10  |All

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14024] Quits unexpectedly after 5 mins

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14024

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> (In reply to Joakim Koed from comment #0)
> > Usually happens after about 5 mins (no matter if I do a live capture, or
> > just analyse a saved capture. After clicking around for a few mins, it
> > crashes :(
> 
> Is there any update regarding this crash?  Does the crash still happen using
> the latest stable version of Wireshark (currently 2.6.6)?

There's been no feedback so I'm assuming there's no problem with the latest
stable version of Wireshark and will close the bug.  If a problem is found,
then feel free to reopen the bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14284] Horrible slow/sluggish UI in High Sierra (macOS 10.13)

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14284

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #15 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #14)
> (In reply to Alexis La Goutte from comment #13)
> > Can you try last 2.9 nighty build ?
> 
> Any feedback?  Can this bug be closed now?

No feedback, so I'm closing this bug as fixed.  If there's still a slowness
problem found, then feel free to reopen the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

--- Comment #1 from Guy Harris  ---
(In reply to Christopher Maynard from comment #0)
> Inconsistent use of -v vs. -V is also annoying and confusing.

editcap and mergecap are the only programs I can see that use -V for the
version; that's because they use -v for "verbose" (and may have done so before
they had a flag to print the version).

Fixing the inconsistency would mean either

1) changing most programs to use -V for version, and changing TShark and
TFShark to use -v for verbose;

2) changing editcap and mergecap to use -v for version and to use -V for
verbose.

Eliminating the inconsistency without potentially breaking some user habits and
scripts is impossible; I suspect 2) would be less painful than 1).

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14306] Export time shift packets into new pcapng file.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14306

Christopher Maynard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #8 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #7)
> (In reply to Gerrit Code Review from comment #4)
> > Change 31057 had a related patch set uploaded by Michael Mann:
> > TimeShiftDialog should be considered an "edit" operation
> > 
> > https://code.wireshark.org/review/31057
> 
> There's a lengthy discussion about use cases in comment 6, but that aside,
> doesn't this patch resolve this bug?  Can it be closed now?

I'm going to assume it's OK to close this bug now.  If someone feels that it
should remain open for some reason, then feel free to reopen it.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14537] Can't update, says program currently running

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14537

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> Can you install Wireshark 2.6.5 from
> https://www.wireshark.org/download/win64/ and then try "Help -> Check for
> Updates..." to try to have Wireshark updated to 2.6.6 (the current latest
> stable release) and report back your findings?  If Wireshark still indicates
> that you need to close the application even after closing it, then maybe you
> could check to see what Task Manager indicates is still running?  It might
> not be Wireshark itself holding things up, but perhaps it's mmdbresolve.exe.
> If the problem no longer occurs, then we can close the bug.

No feedback so I'm assuming this is no longer a problem.  If that's not the
case, then feel free to reopen the bug and update the relevant information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15483] New: Some command-line tools don't document the version option in their help output and some are missing help altogether

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15483

Bug ID: 15483
   Summary: Some command-line tools don't document the version
option in their help output and some are missing help
altogether
   Product: Wireshark
   Version: Git
  Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
  Severity: Minor
  Priority: Low
 Component: Extras
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: christopher.mayn...@igt.com
  Target Milestone: ---

Build Information:
Version 3.1.0 (v3.1.0rc0-8-g53b55bfb)

Compiled (64-bit) with Qt 5.12.1, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729.

Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Xeon(R) CPU
E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with
locale English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with AirPcap 4.1.0 build
1622, binary plugins supported (14 loaded).

Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730). 
--
The following tools *do* document their version option in the " -h"
output:
1) dumpcap -v is documented
2) rawshark -v is documented
3) tshark -v is documented
4) Wireshark -v is documented

The following tools are missing their version option from the " -h"
output:
1) capinfos -h is missing the -v option
2) editcap -h is missing the -V option
3) mergecap -h is missing the -V option
4) reordercap -h is missing the -v option
5) text2pcap -h is missing the -v option

The following tools don't implement either a version or help option
1) captype
2) dftest
3) idl2wrs
4) lemon
5) mmdbresolve
6) randpkt
7) sharkd

I suppose there's nothing to be done with either lemon or mmdbresolve. 
Inconsistent use of -v vs. -V is also annoying and confusing.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15482] New: editcap can't convert a NetMon 2.x capture file to pcapng, even though Wireshark can do it.

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15482

Bug ID: 15482
   Summary: editcap can't convert a NetMon 2.x capture file to
pcapng, even though Wireshark can do it.
   Product: Wireshark
   Version: Git
  Hardware: x86-64
OS: Windows 10
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: Extras
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: christopher.mayn...@igt.com
  Target Milestone: ---

Created attachment 16897
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=16897&action=edit
Microsoft NetMon 2.x file with Ethernet encapsulation

Build Information:
Version 3.1.0 (v3.1.0rc0-8-g53b55bfb)

Compiled (64-bit) with Qt 5.12.1, with WinPcap SDK (WpdPack) 4.1.2, with GLib
2.52.2, with zlib 1.2.11, with SMI 0.4.8, with c-ares 1.14.0, with Lua 5.2.4,
with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with MIT Kerberos,
with MaxMind DB resolver, with nghttp2 1.14.0, with LZ4, with Snappy, with
libxml2 2.9.9, with QtMultimedia, with AirPcap, with SBC, with SpanDSP, with
bcg729.

Running on 64-bit Windows 10 (1809), build 17763, with Intel(R) Xeon(R) CPU
E3-1505M v5 @ 2.80GHz (with SSE4.2), with 16225 MB of physical memory, with
locale English_United States.1252, with Npcap version 0.99-r9, based on libpcap
version 1.8.1, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with AirPcap 4.1.0 build
1622, binary plugins supported (14 loaded).

Built using Microsoft Visual Studio 2017 (VC++ 14.15, build 26730).
--
editcap -F pcapng 7620-Native_NetMon_Ethernet.cap
7620-Native_NetMon_Ethernet.pcapng
editcap: The capture file being read can't be written as a "pcapng" file.

Loading the pcapng 7620-Native_NetMon_Ethernet.cap capture file into Wireshark
and choosing "File -> Save As..." and specifying a pcapng file format does work
though.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 14772] IO Graph and Y Field Analysis is not working correctly

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14772

Christopher Maynard  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Christopher Maynard  ---
(In reply to Christopher Maynard from comment #1)
> Can you try again with the latest stable version of Wireshark (currently
> 2.6.6)?  I can't reproduce this bug using that version.

Since I can't reproduce this bug and no feedback was provided, I'm going to
assume that this problem no longer exists and close the bug.  I don't know if
there was a bug and it was fixed, just that it works for me, so that's the
status I'm using.

If this bug can be reproduced again with the latest stable version of
Wireshark, then feel frree to reopen the bug and update the relevant
information.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15218] Linux Mint 19 - When attempting to play stream, Wireshark freezes, generates large temp files, and 100% CPU usage

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15218

Jason Paul  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
Version|2.6.4   |2.6.6

--- Comment #4 from Jason Paul  ---
FYI this was confirmed by another user on the Linux Mint forums:

https://forums.linuxmint.com/viewtopic.php?t=279861

Still experiencing this issue on Wireshark 2.6.6.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 15481] New: Add additional decimal places to the RTP Analysis Delta field

[bugzilla-daemon]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15481

Bug ID: 15481
   Summary: Add additional decimal places to the RTP Analysis
Delta field
   Product: Wireshark
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Common utilities (libwsutil)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: nat...@nathandixon.co.uk
  Target Milestone: ---

Build Information:
Version 2.4.0 (v2.4.0-0-g9be0fa500d)

Copyright 1998-2017 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.9.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
with
SBC, with SpanDSP.

Running on 64-bit Windows 10, build 15063, with Intel(R) Core(TM) i5-7300U CPU
@
2.60GHz (with SSE4.2), with 8071 MB of physical memory, with locale
English_United Kingdom.1252, with WinPcap version 4.1.3 (packet.dll version
4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008), with
GnuTLS 3.4.11, with Gcrypt 1.7.6, without AirPcap.

Built using Microsoft Visual C++ 14.0 build 24215

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Whilst packet delta time is displayed to 6 decimal places in the main display,
the Telephony/RTP_Analysis display only shows it to 2 places.

When analysing very high packet rates e.g. SMPTE2022-6 video
(270,1500,3000Mb/s), the lack of granularity for this timing display is
prohibitive.

Please add additional decimal places, or enable the measurement unit to be
adjusted, perhaps.

Thank you.

-- 
You are receiving this mail because:
You are watching all bug changes.___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe