a bug in Windows10 which change network adapt's IP Address
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
ncap packet driver will case the problem which makes the network adapt's IPv4 Address automatic change to 169.254.29.x likes 169.254.29.28, no matter the network adapt is Virually or is truely exist.
and other people also meet this problem: https://github.com/SoftEtherVPN/Win10Pcap/issues/20#issuecomment-712768842
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 IPv4 change on Windows 10 with the Npcap packet driver, then compare the behavior with the linked Win10Pcap report. The issue does not name source files or tests; done means a virtual or physical adapter keeps its configured IPv4 address while Npcap is installed and used.
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
- 30/100