Microsoft Azure VFP Switch Filter Extension dropping packets from the external device (not the host)

[PatelRajeshK]

Windows Version

Microsoft Windows 11 26200.8893

WSL Version

2.7.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.18.33.2-2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Here is my WSLConfig file.
[wsl2]
memory=8GB
processors=4
networkingMode=mirrored
dnsTunneling=true
firewall=true
autoProxy=true

[experimental]
hostAddressLoopback=true
sparseVhd=true

I am running Sql Server linux container inside wsl to host DB. Connection from the host to container on port 1433 works fine because of the hostAddressLoopback set to true to WSLConfig but when external machine tries to connect to same container using host ip it fails to connect. I have set True to DefaultInboundAction/DefaultOutboundAction for NetFirewallHyperVVMSetting. After analyzing the packets captured using pktmon I found that FSE switch adapter was dropping the packet with error code Invalid Packet. So I after few trials I found that when I disable Microsoft Azure VFP Switch Filter Extension everything works fine and it is turned on same error occurs.

Expected Behavior

Since Microsoft Azure VFP Switch Filter Extension gets enabled by default mirrored mode networking to WSL should work fine with this filter extension on.

Actual Behavior

When the Microsoft Azure VFP Switch Filter Extension is enabled on FSE Switch external connection to WSL does not work in mirrored mode.

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 script will output the path of the log file once done.

If this is a networking issue, please use .\collect-wsl-logs.ps1 -LogProfile networking instead, following the instructions in Collect WSL logs for networking issues

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

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[PatelRajeshK]

I analyzed the collected logs and it captures so much information from the environment sorry but I am not able to post it on public repo

[PatelRajeshK]

/emailed-logs

[github-actions]

Diagnostic information

Found '/emailed-logs', adding tag 'emailed-logs'