Please enable CONFIG_NFT_SOCKET in the WSL2 Kernel
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux
- Domain
- operating-systems
Research direction
This is a kernel config tweak: CONFIG_NFT_TPROXY is already enabled in arch/arm64/configs/config-wsl-arm64 around line 1397, but the matching CONFIG_NFT_SOCKET symbol is missing. Add it there and in the x86_64 WSL config (usually arch/x86/configs/config-wsl), matching the =m/=y style of the neighbouring netfilter options. Verify by rebuilding and confirming modprobe nft_socket succeeds; done means the symbol is in the shipped configs and the module loads.
Written by the indexing model from the issue text.
Description
Hi, CONFIG_NFT_TPROXY is properly enabled in the kernel , meaning it supports TPROXY (typically used by squid for instance) yet CONFIG_NFT_SOCKET isn't. It's slightly annoying because it's a pretty important optimization; for instance the example in the official documentation https://docs.kernel.org/networking/tproxy.html doesn't work because of it.
modprobe: FATAL: Module nft_socket not found in directory /lib/modules/6.6.87.2-microsoft-standard-WSL2
Would it be possible to enable the module please? :D
Have a great end of week !
- Dominant language
- C++
- Stars
- 34.4k
- Forks
- 1.9k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 166
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/WSL
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/WSL#42114 · 3 comments ·
Maintainers usually reply within 1 day
-
feature kernel wsl2
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/WSL#41107 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature kernel
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
microsoft/WSL#41054 · 9 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature GPU
Difficulty 1/5 1-3 hours Newbie friendliness 70/100
microsoft/WSL#13592 · 4 comments ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
microsoft/WSL#11458 · 6 comments · 8 reactions ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nextcloud/passman-android#214 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
2026.11.0 fails to install on Intel macOS: requirements.txt pins cryptography==50.0.2 for Darwin x86_64May be free again A pull request for this issue was closed without being merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 87/100
esphome/esphome#22892 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
distante/esphome-components#50 · 1 comment ·
Maintainers usually reply within 1 day
-
agent:Windows enhancement pri:medium release windows
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day