Some packet loss after reconnect the cable
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
I’m capturing a profinet-connection between an plc and a device with wireshark V3.4.3 and npcap V1.10
Before I unplug and re-connect the cable physically, I can see all the profinet-broadcast “ident”-telegrams send out of the plc. After the connection loss, there are no “ident”-telegrams received anymore. I have to stop the capturing and restart it. I tested with Windows Build 20H2 (19042.804).
I tried the same with an own capturing-App written in c# it used the open source project “sharppcap”. The same behavior occurs…
For the next test i tried the same at a PC with an older Windows-Build 1909 (18363.1256), Wireshark 3.4.3, Npcap v1.10.
It works!!!
It seems the Windows-Build breaks something in the capturing?!?!
Is there any fix for the problem?
Thanks in advance
Contributor guide
No contributing guide indexed for this repository
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 reproducing the packet-capture behavior on Windows Build 20H2 with Wireshark 3.4.3 and Npcap 1.10, then compare it with Build 1909, where the reporter says it works. Check whether the same failure occurs through the reported SharpPcap application. Done means identifying a reproducible cause or confirming a specific fix or workaround for reconnect handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100