microsoft / microsoft/WSL

WSL2 can't access IPv6 addresses in mirrored mode

Open
#12,615 7 comments 1 reaction 0 assignees View on GitHub
emailed-logs network
Dominant language
C++
Stars
33.7k
Forks
1.8k
Avg merge
3d 17h
Merged PRs (30d)
116

Description

### Windows Version

Microsoft Windows [Version 10.0.26100.3194]

### WSL Version

2.4.11.0

### Are you using WSL 1 or WSL 2?

- [x] 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_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with WSL 2.4.11.0, Debian 12, kernel 5.15.167.4, and networkingMode=mirrored in .wslconfig. Compare the listed PowerShell and WSL2 ping commands for ipv4.google.com and ipv6.google.com; done means both IPv4 and IPv6 pings work from WSL2 as they do on Windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, debian
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.