search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.34k stars 814 forks source link

Option to explicitly specify static IP range for WSL2 #12155

Open zkorhone opened 4 hours ago

zkorhone commented 4 hours ago

Is your feature request related to a problem? Please describe. I can not use automatically randomly generated network ranges on my workstation.

Describe the solution you'd like Allow to set static range in the configuration file. Apply the requested configuration when creating NAT device

Describe alternatives you've considered Changing Operating System vendor. This issue has been ignored for ages without any comments: https://github.com/microsoft/WSL/issues/4467 . There's many similar issues pending for what seems to be extremely trivial to fix on WSL side.

Using mirrored mode. But that's a no-go. It's completely undocumented from security perspective. I have fears that it will effectively bridge Windows through WSL2 in public network without applying security policies. I'm not willing nor have I time to manage WSL2 firewall configuration.

Additional context Add any other context or screenshots about the feature request here.

github-actions[bot] commented 4 hours ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com 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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.