nmap / nmap/npcap

Npcap Bug Report

Open
#651 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
3.6k
Forks
592
PR merge metrics
No merged PRs in 30d

Description

Hi ,
I have a question regarding to NPCAP/WIN10PCAP.
We have a wire connection between our application(UI) and Embedded system . Which they sent to each other real time packets ( data ) via NPCAP.
it is working fine when the cable connected in both sides; ( embedded side , UI side ) with Ethernet 1Gbs adapters.

The problem is that the connection does not work when the application(UI) sends/receives packets via 2.5Gbs Ethernet Adapter while the Embedded ethernet adapter is 1Gbs.
it works only if both NPCAP+Win10Pcap are downloaded.
So with Win10Pcap+Npcap together the specific scenario is working.

The question is: why do we need to download also Win10Pcap to make the specific scenario working? What is the relationship between Win10Pcap and 2.5Gbs adapter?

We hope you will reply as soon as possible because our project is stuck in this issue.

Thank you in advance.
Firas.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository files or tests are named. Start by reproducing the reported setup with Npcap and Win10Pcap, comparing a 2.5Gb Ethernet adapter connected to a 1Gb adapter with each installation; done means explaining why both installations are required for packet exchange.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.