Sending many custom frames with npcap on an interface cause corruption in the other frames sent from the interface.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
We are using the npcap library to send EtherCAT frames to an EtherCAT network (a packet every few milliseconds).
The windows protocols are still active, we cannot deativate them.
The EtherCAT network is tolerant to non EtherCAT ethernet frames,
but it happen that, when pcap is in use to send the EtherCAT frames, some Windows frames (ie. DHCP request) exit corrupted, and alters the error counters of the EtherCAT slaves.
There isn't any problem on the frames sent by the npcap library.
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 issue with npcap sending EtherCAT frames while Windows protocols remain active, and capture the affected DHCP or other Windows frames alongside the npcap traffic. Done means Windows-originated frames are no longer corrupted during concurrent EtherCAT transmission; the issue names no source files or tests to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100