PCAP_OPENFLAG_NOCAPTURE_LOCAL behaviour
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Let's say we have 2 pcap_t handles A1 and A2 for the same adapter A.
In WinPCAP:
Packets tx on A1 are also rx on both A1 and A2. If we open A1 with flag PCAP_OPENFLAG_NOCAPTURE_LOCAL, the packets tx on A1 will not be rx on A1, but will still be rx on A2.
I see similar behavour with npcap v0.9990.
However, a user of my app who has npcap v1.10 reports a behaviour where it looks like the packets tx on A1 (opened with PCAP_OPENFLAG_NOCAPTURE_LOCAL flag) are not rx on A2.
I don't see anything in the npcap changelog that suggests a change in this behaviour since v0.9990.
Please clarify on the npcap behaviour and if there is any change across versions.
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
No source files or tests are named. Start by locating the handling of PCAP_OPENFLAG_NOCAPTURE_LOCAL, then compare behavior with two handles on the same adapter across npcap v0.9990 and v1.10. Done means the version-specific behavior is reproduced and clearly documented.
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