[Help] Why npcap does not capture winpkfilter diverted packets?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
Hello recently I realised that Wireshark (Npcap based) wasn't showing diverted NAT packets from a router app called Connectify. Which is implemented using WinPkFilter.
I can't see arriving packets to the nat Interface, only the ones which are directed to its own ip.
It seems that winpkfilter is hooking or something lower than npcap.
I would like to know if is possible to get those packets or whats happening.
Thanks, Greetings
PD: Haven't tried Windivert based apps but I may asume the same behaviour because they're implemented via WFP with same purposes.
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 reviewing the issue’s description of Npcap, WinPkFilter, and WFP packet interception, then determine whether diverted NAT packets are expected to be visible at Npcap’s capture layer. Done means a confirmed explanation of the interception behavior and, if supported, a clearly identified entry point or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100