Telegram loss in Profinetsniff with Scapy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12.6k
- Forks
- 2.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 56
Description
Brief description
The telegram transcript in Scapy does not appear to be complete. Telegrams that are present in a reference recording with Wireshark are missing. During the telegram recording, 3 profinet alarms were triggered. Wireshark was able to capture all telegrams.
Scapy only recognised one of these alarm telegram frames.
A recording via Wireshark and one with Scapy are attached.
Protocol:
PNIO
Scapy version
2.5.0
Python version
2.7.16
Operating system
Raspbian 10 Buster
Additional environment information
No response
How to reproduce
Actual result
Expected result
Related resources
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining pnio_alarm.txt and comparing the supplied packages.zip and dump.zip recordings with the reported Scapy 2.5.0 behavior. Reproduce the PNIO capture and identify why alarm telegram frames are missing compared with Wireshark. Done means the relevant alarm telegrams are recognized and included in the Scapy transcript.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100