Skip to content
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

Closed
zkorhone opened this issue Oct 11, 2024 · 2 comments
Closed

Option to explicitly specify static IP range for WSL2 #12155

zkorhone opened this issue Oct 11, 2024 · 2 comments

Comments

@zkorhone
Copy link

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.

Copy link

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
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.

Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant