Cannot use existing Wintun adapter by name (breaking change since latest official v26.3.27)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 41.7k
- Forks
- 5.9k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 29
Description
NewTun is documented as
https://github.com/XTLS/Xray-core/blob/c412e77a9b712082ac9ebf27fa793951cb5a7d85/proxy/tun/tun_windows.go#L50-L52
I relied on this behavior: created and configured custom Wintun adapter as well as Windows Filtering Platform rules before launching xray.exe
For unclear reason, the call to wintun.OpenAdapter was removed in #5887 (diff). So now the use case is broken.
cc @LjhAUMEM
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 at the documented NewTun entry point in proxy/tun/tun_windows.go and compare its current Wintun handling with the behavior removed in PR #5887. Confirm that a pre-created Wintun adapter can again be selected by name when xray.exe starts, without disrupting the caller's existing Windows Filtering Platform rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100