microsoft / microsoft/Windows-classic-samples
Network/NDIS/MUX device driver project is not working in a hyper-v virtual environment generation 2
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
The NDIS intermediate driver developed some 26 years ago, is not working well in virtual environment.
I suggest to change the implementation to a newer NDIS version , and add neccessary handling for a dynamic network environment
1. Move the Driver Contract to NDIS 6.30
2. Use NDIS 6.30 Miniport General Attributes
3. Add Updated Power Management Capabilities
4. Add Honest Hardware-Assist Capability Reporting
5. Add RSS Pass-Through
6. Avoid Promiscuous Mode Unless It Is Actually Requested
7. Correct the Virtual Miniport INF Lower Edge
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
The issue does not identify the driver files, INF, tests, or entry points to inspect. Start by locating the NDIS intermediate driver and its virtual miniport INF, then compare the implementation with the requested NDIS 6.30 capabilities. Done means the driver works in a Generation 2 Hyper-V environment with correct capability, power-management, RSS, promiscuous-mode, and INF behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100