TUN_IFACE_CREATE, cannot acquire TAP handle
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 467
- PR merge metrics
- No merged PRs in 30d
Description
When I use openvpn3, I get an error when I use TapWindows6.
[Log]Fri Aug 26 10:38:08 2022 TAP ADAPTERS:Open TAP device "" PATH="" FAILED
[Log]Fri Aug 26 10:38:08 2022 TUN Error: cannot acquire TAP handle
[Event]Fri Aug 26 10:38:08 2022 TUN_IFACE_CREATE, cannot acquire TAP handle, error:1, fatal:1
When TAP_WIN_COMPONENT_ID is defined as tap0901, tun can be created,Why does TAP_WIN_COMPONENT_ID have no defined value?
Does Windows use TapWindows driver in openvpn3 need admin privileges?
Contributor guide
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 Windows TapWindows6 failure using the log sequence in the issue, then trace the openvpn3 Windows TAP handle creation path and the definition or use of TAP_WIN_COMPONENT_ID. Check how the tap0901 value changes behavior and verify whether administrator privileges affect creation. Done means the cause and required configuration or privilege are identified and the issue's behavior is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- 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