Config windows to use WSL2 IPTABLES FW for all traffic
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
I would like to use WSL FW instead of Windows, allowing all IPTABLES functions as mangle for all communications to the network. Windows NDIS or firewall will not allow me to set TTL/HOP by app port.
I would like WSL2 stack to selectively replace windows NDIS STACK.
I would like this to be a Windows Control panel easy to choose selection.
NDIS, nor Windows Firewall allow any such capabilities as can be done by Linux without coding software.
I want to be able to have advanced IPTABLES mangle table config without software or 3rd party added software.
Thanks
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 reviewing the WSL2 networking path and its interaction with Windows NDIS and the firewall. The requested result is a Windows Control Panel choice that lets WSL2 selectively replace the Windows network stack and supports iptables mangle rules for all communications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- networking, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100