Please enable CONFIG_NFT_SOCKET in the WSL2 Kernel

Open Beginner friendly
#42,306 3 comments 0 reactions 0 assignees View on GitHub

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

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

feature wsl2

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/WSL

All issues in microsoft/WSL

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.