Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Register
  • Sign in
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,360
    • Issues 1,360
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 175
    • Merge requests 175
  • 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 FoundationWireshark Foundation
  • wiresharkwireshark
  • Issues
  • #18167
Closed
Open
Issue created Jun 30, 2022 by Ahmad Bataineh@IPMasters

Incorrect type for the IEC 60870 APDU appears in packet details pane

Summary

(Summarize the bug encountered concisely)

Steps to reproduce

(How one can reproduce the issue - this is very important)

What is the current bug behavior?

Incorrect type for the IEC 60870 APDU appears in packet details pane, there are three different APDU frames types (I-frame, S-frame and U-frame). The "Type" field under the "ApduLen" field is not correct. While the type is correctly displayed in "info" column in packet list pane.

What is the expected correct behavior?

The type is determined based on the value of the last two bits of the byte nest to "ApduLen" byte, and not determined by the first two bits of this byte as the Wireshark parser behaves.

Sample capture file

attached 104pcap.pcap file, example of such packets are packets no. 77, 79, 83 and others.104pcap.pcap

Relevant logs and/or screenshots

104pcap-WiresharkBug

Build information

(In Wireshark, select Help->About Wireshark from the main menu and use the button "Copy To Clipboard".
Please paste the complete output here. Or from the command line, run `tshark -v` or `wireshark -v`)
Edited Jun 30, 2022 by Guy Harris
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking