-
Notifications
You must be signed in to change notification settings - Fork 858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue using iptables with 6.6.36-lts kernel #11884
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
Attached wsl logs to appease bot. |
The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running. Diagnostic information
|
Just attaching logs to appease bot: (These are the incorrect logs; but the logs don't even matter for this issue) |
Diagnostic information
|
@nnathan in case you missed the release notes, emphasis on the custom kernel:
Also, after cloning the repository delete First try loading manually the required modules or build a kernel with the modules included. |
I did actually heed that warning but I couldn't get the kernel to boot when everything is not a module. I did this:
Then I set the kernel in I get the following: Kernel Console
Specifically the bottom part is the issue:
I'm not sure what to do - any suggestions? |
The latest WSL kernel (6.6.36.3-microsoft-standard-WSL2) already supports masquerading:
After running your iptables commands this is the output of the
List of all modules in the netfilter included in the default WSL2 kernel:
However, if you want to experiment with custom kernels, please do! |
Actually I noticed the default kernel is now |
|
I am wondering what issues made the Kernel to be reverted to version 5.15.x ? |
same question here. why revert and not upgrade to 6.10.4? (or 6.6.45 lts) greetings |
Just my 2ct... |
Note that the EOL of versions 5.15 and 6.6 are very similar (Oct. 2026 vs Dec. 2026). Upgrading takes a lot of work, and upgrading to 6.6 will have little benefit. I believe it would be better for Microsoft to wait and update to a future Kernel version (maybe 7.x ?) that has a longer support time. Waiting won't be a problem as the current version 5.15 has security and bug fix support until 2026. |
Windows Version
Microsoft Windows [Version 10.0.22631.3880]
WSL Version
2.3.13.0
Are you using WSL 1 or WSL 2?
Kernel Version
6.6.36.3-microsoft-standard-WSL2+
Distro Version
Ubuntu 24.04 LTS
Other Software
iptables v1.8.10 (nf_tables)
Repro Steps
Build the kernel first:
Edit
~/.wslconfig
:Shutdown WSL2
Start WSL2
Verify kernel:
Now run iptables command:
Expected Behavior
This should work as it does in the 5.15 kernel.
Actual Behavior
iptables doesn't work with MASQUERADE target which pretty much also means Docker is unusable.
Diagnostic Logs
The text was updated successfully, but these errors were encountered: