-
Notifications
You must be signed in to change notification settings - Fork 821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to explicitly specify static IP range for WSL2 #12155
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 View similar issuesPlease 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:
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
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: #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.
The text was updated successfully, but these errors were encountered: