Need to be able to assign a specific cidr range for DHCP in WSL2 distros
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
When I connect to my corporate VPN they use the CIDR range 172.16.0.0\16 which seems to always conflict with the CIDR range being used by Hyper-V / WSL so I cannot connect to the internet from the WSL distro, and sometimes not even connect to my corporate network if the IP address assigned happens to already be in use.
Describe the solution you'd like
I would like to be able to assign a specific CIDR range for use by the Hyper-V Default Switch &| the WSL vswitch.
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 investigating how the Hyper-V Default Switch and the WSL vswitch currently select CIDR ranges, using the reported 172.16.0.0/16 conflict as the reproduction case. Done means users can assign a specific CIDR range to these switches without breaking WSL or corporate VPN connectivity; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100