Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,337
    • Issues 1,337
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 151
    • Merge requests 151
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Wireshark Foundation
  • wiresharkwireshark
  • Issues
  • #17763
Closed
Open
Created Dec 03, 2021 by Torsten Sorger@TorstenSorger

Command line option "-o console.log.level" causes wireshark and tshark to exit on start

Summary

Unexpected termination if custom logging level is set via commandline options. Also affecting "Export to Wireshark" from Riverbeds Packet Analyzer Plus (Bug ID AR-2617 at Riverbed).

Steps to reproduce

Run Wireshark or tshark from the commanline with extra argument "-o console.log.level:127"

What is the current bug behavior?

Wireshark/tshark exits after starting with the message: "specifies obsolete preference" (Wireshark) / "specifies unknown preference" (tshark)

What is the expected correct behavior?

Pre version 3.6.0 the logging level could be set by this option and messages depending on the severity were shown in the console. Also Wireshark did not exit when providing this parameter.

Sample capture file

Not applicable

Relevant logs and/or screenshots

Microsoft Windows [Version 10.0.19044.1348]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\username>tshark -o console.log.level:127
tshark: -o flag "console.log.level:127" specifies unknown preference

C:\Users\username>wireshark -o console.log.level:127

wireshark: -o flag "console.log.level:127" specifies obsolete preference

Build information

3.6.0 (v3.6.0-0-g3a34e44d02c9)

Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.29, build 30040),
with Qt 5.15.2, with libpcap, with GLib 2.66.4, with zlib 1.2.11, 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.44.0, with brotli, with LZ4,
with Zstandard, with Snappy, with libxml2 2.9.10, with libsmi 0.4.8, with
QtMultimedia, with automatic updates using WinSparkle 0.5.7, with AirPcap, with
SpeexDSP (using bundled resampler), with Minizip.

Running on 64-bit Windows 10 (21H2), build 19044, with Intel(R) Core(TM)
i5-8350U CPU @ 1.70GHz (with SSE4.2), with 16243 MB of physical memory, with
GLib 2.66.4, with Qt 5.15.2, with Npcap version 1.55, based on libpcap version
1.10.2-PRE-GIT, with c-ares 1.17.0, with GnuTLS 3.6.3, with Gcrypt 1.8.3, with
nghttp2 1.44.0, with brotli 1.0.9, with LZ4 1.9.3, with Zstandard 1.4.0, without
AirPcap, with light display mode, without HiDPI, with
LC_TYPE=German_Germany.utf8, binary plugins supported (21 loaded).
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking