Suggest using NAT44 and NAT66 or DHCPv6 with relay mode
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.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
1. I want to use IPV6.
2. I've tried using mirrored network mode, but it caused that all my network connections on windows including zerotier and tailscale have been mirrored. I can't choose whether or not which network connection can mirrored.
3. When I turn on different WSLs. The IP is same in NAT mode and mirrored mode. If ip is different, it will be better to connect to different WSLs.
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
IPV4 mode: NAT44
IPV6 mode: dhcpv6 relay ( I have ipv6 with 64 prefixlen and my router offer dhcpv6 server )
```[tasklist]
### Tasks
- [ ] Add NAT66 and dhcpv6 mode.
```
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
No files, tests, or entry points are named. Start by clarifying how NAT44, NAT66, and DHCPv6 relay mode should interact with WSL's existing NAT and mirrored modes, then identify the relevant networking implementation and tests. Done means the requested IPv4 and IPv6 modes work without mirroring unrelated Windows connections and allow distinct WSL addresses.
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
- Needs clarification
- Newbie friendliness
- 25/100