setsockopt TLS_TX: Protocol not available

[s1111111111c]

Windows Version

Microsoft Windows [Version 10.0.22631.3593]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.1.21.2-microsoft-standard-WSL2+

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

I have enabled the kTLS module (by modifying the kernel config, compiling etc ) , however even though the module is active, I cannot get the kTLS to work.

if (setsockopt(sockfd, SOL_TLS, TLS_TX, &crypto_info, sizeof(crypto_info)) < 0) {
   perror("setsockopt TLS_TX");
   close(sockfd);
   return 1;
}

Output
setsockopt TLS_TX: Protocol not available

But the module is loaded
$ lsmod | grep tls tls 131072 0

Expected Behavior

kTLS was working

Actual Behavior

Actually doesnt work even if my kernel have module

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

[s1111111111c]

WslLogs-2024-06-04_15-41-29.zip

[github-actions]

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

.wslconfig found
	Custom kernel found: 'C:\wsl-kernel\bzImage'
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

[s1111111111c]

I reproduced the issue

[OneBlue]

Hi @s1111111111c.

WSL doesn't have any control on what happens inside custom kernels / modules. I don't have deep knowledge of how kTLS works, but that's not something that WSL has an influence on.

Closing since this issue is external.