WSL2 can't access IPv6 addresses in mirrored mode

[recatek]

Windows Version

Microsoft Windows [Version 10.0.26100.3194]

WSL Version

2.4.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4

Distro Version

Debian 12

Other Software

No response

Repro Steps

Run WSL2 with the following .wslconfig:

[wsl2]
networkingMode=mirrored

In Powershell on the Windows side, ping ipv4.google.com and ipv6.google.com.

In WSL2 Debian 12, ping ipv4.google.com and ipv6.google.com.

Expected Behavior

The IPv4 and IPv6 pings should work on both the PowerShell side and the WSL2 Debian side.

Actual Behavior

PowerShell:

ping ipv4.google.com

Pinging ipv4.l.google.com [142.251.179.100] with 32 bytes of data:
Reply from 142.251.179.100: bytes=32 time=10ms TTL=104
Reply from 142.251.179.100: bytes=32 time=10ms TTL=104
Reply from 142.251.179.100: bytes=32 time=9ms TTL=104
Reply from 142.251.179.100: bytes=32 time=9ms TTL=104

ping ipv6.google.com

Pinging ipv6.l.google.com [2607:f8b0:4004:c1f::8b] with 32 bytes of data:
Reply from 2607:f8b0:4004:c1f::8b: time=8ms
Reply from 2607:f8b0:4004:c1f::8b: time=8ms
Reply from 2607:f8b0:4004:c1f::8b: time=8ms
Reply from 2607:f8b0:4004:c1f::8b: time=8ms

WSL2 Debian 12:

ping ipv4.google.com
PING ipv4.l.google.com (172.253.62.102) 56(84) bytes of data.
64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=1 ttl=57 time=9.16 ms
64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=2 ttl=57 time=9.88 ms
64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=3 ttl=57 time=9.25 ms
64 bytes from bc-in-f102.1e100.net (172.253.62.102): icmp_seq=5 ttl=57 time=9.81 ms

ping ipv6.google.com
PING ipv6.google.com(pd-in-f139.1e100.net (2607:f8b0:4004:c1f::8b)) 56 data bytes
From 2605:a601:a693:5001:3151:4839:9d23:a8cc icmp_seq=1 Destination unreachable: Address unreachable
From 2605:a601:a693:5001:3151:4839:9d23:a8cc icmp_seq=2 Destination unreachable: Address unreachable
From 2605:a601:a693:5001:3151:4839:9d23:a8cc icmp_seq=3 Destination unreachable: Address unreachable
From 2605:a601:a693:5001:3151:4839:9d23:a8cc icmp_seq=4 Destination unreachable: Address unreachable

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-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
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'.

[recatek]

/emailed-logs

Sent via Feedback tool as the collect-networking-logs.ps1 script crashed on my machine.

[github-actions]

Diagnostic information

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