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,344
    • Issues 1,344
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 156
    • Merge requests 156
  • 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
  • #18005
Closed
Open
Created Mar 17, 2022 by K Wang@spk951218

Goose Packet Expert Information

Summary

Hi, my team wants to show detailed expert information for Goose packet (IEC61850). The current wireshark shows:

[Malformed Packet: GOOSE]

  [Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]

    [Malformed Packet (Exception Occurred)]

    [Severity level: Error]

    [Group: Malformed]

I asked in the wireshark Q&A forum, they recommend me to report here

Steps to reproduce

Dissecting our goose packet

What is the current bug behavior?

Only Exception Occurred is shown, no detailed information

What is the expected correct behavior?

This goose packet's "numDataSetEntries" field is wrong, we expect wireshark to report it

Sample capture file

The capture file is attached goos.pcap

Relevant logs and/or screenshots

Screenshot malformed

Build information

3.7.0 (v3.7.0rc0-1455-gf43ce70fd9cc)

Compiled (64-bit) using Microsoft Visual Studio 2019 (VC++ 14.29, build 30140),
with GLib 2.66.4, with PCRE2, with zlib 1.2.11, with Qt 5.15.2, with libpcap,
with Lua 5.2.4, with GnuTLS 3.6.3 and PKCS #11 support, with Gcrypt 1.8.3, with
Kerberos (MIT), with MaxMind, 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 (20H2), build 19042, with Intel(R) Core(TM)
i5-6300U CPU @ 2.40GHz (with SSE4.2), with 16264 MB of physical memory, with
GLib 2.66.4, with PCRE2 10.39 2021-10-29, with Qt 5.15.2, with Npcap version
1.31, based on libpcap version 1.10.1-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, with AirPcap 4.1.0 build 1622, with light display
mode, with HiDPI, with LC_TYPE=English_United States.utf8, with binary plugins
(21 loaded).
Edited Mar 18, 2022 by K Wang
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking