Document WSL2 inbound P2P connectivity - #622
Merged
Merged
Conversation
Inbound IPv6 does not reach Docker containers on WSL 2. Verified with WSL 2.9.12 on Windows build 26200: a listener running directly in WSL is reachable over IPv6, while a published container port is not, and inbound IPv4 to that same published port succeeds at the same moment. Not a firewall issue, it persists with the Hyper-V firewall set to allow all inbound and with matching Windows Defender Firewall rules. Inbound IPv4 needs explicit Hyper-V firewall rules. That firewall is a separate layer from Windows Defender Firewall, governs traffic into the WSL VM, and blocks inbound by default. Also notes wslc as a direction to watch, should it gain Compose support. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
yorickdowne
force-pushed
the
wsl-inbound-p2p
branch
from
September 19, 2026 13:38
8d9e63c to
18ea42c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Inbound IPv6 is not delivered to processes inside WSL 2. Verified with WSL 2.7.12 on Windows build 26200, with the Hyper-V firewall set to allow all inbound and matching Windows Defender Firewall rules in place, while inbound IPv4 to the same port succeeded at the same moment.
Inbound IPv4 needs explicit Hyper-V firewall rules. That firewall is a separate layer from Windows Defender Firewall, governs traffic into the WSL VM, and blocks inbound by default.