craigloewen-msft
commented
7 months ago Tagging @chanpreetdhanjal for visibility
Open Boilerplate4u opened 8 months ago
craigloewen-msft
commented
7 months ago Tagging @chanpreetdhanjal for visibility
Documentation Issue
While the "mirrored" networking mode in WSL may offer several advantages over the old configuration options, it lacks in-depth documentation on how to set up more advanced configurations like a network bridge. This aspect of the documentation requires urgent improvement.
For example, a network bridge in the context of WSL allows the instance to appear as a separate device on the physical network, offering several benefits:
Direct external access: Devices on your network can communicate directly with the WSL instance using its own IP address.
Enhanced services: You can run services within WSL (e.g., web servers, databases) that are accessible from other devices on the network without complex port forwarding.
Flexible network scenarios: Bridging enables more advanced networking setups, potentially useful for development and testing.
Why the documentation needs improvement:
Focus on basic mirrored mode: Most documentation centers around enabling the base "mirrored" mode without going into the complexities of bridging like how the interfaces are interconneced, etc.
Lack of clear examples: There aren't enough practical, step-by-step guides on how to create a functional bridge for common use cases.
Assumption of internal expertise: The current resources expect users to have a deep understanding of WSL internals and Linux networking tools and bridging concepts.
Link to documentation page
https://learn.microsoft.com/en-us/windows/wsl/networking
Suggested Improvements
Why the documentation needs improvement:
Focus on basic mirrored mode: Most documentation centers around enabling the base "mirrored" mode without going into the complexities of bridging like how the interfaces are interconneced, etc.
Lack of clear examples: There aren't enough practical, step-by-step guides on how to create a functional bridge for common use cases.
Assumption of internal expertise: The current resources expect users to have a deep understanding of WSL internals and Linux networking tools and bridging concepts.