Add feature to allow WSL to work natively on VPN for accessing private Azure resources
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Is your feature request related to a problem? Please describe.
WSL/WSL2 lose connectivity and some functions while on VPN. That creates a problem to access/connect to private resources on azure when using expressroute or other VPN.
Describe the solution you'd like
Add feature or bug fixes to allow WSL/WSL2 to work natively on VPN
Describe alternatives you've considered
Alternatives such as Powershell
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
The issue names no files, tests, or entry points. Start by reproducing WSL/WSL2 connectivity loss while connected to a VPN, including access to private Azure resources through ExpressRoute; done means WSL/WSL2 can access those resources natively while on VPN.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100