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
Add "allow" rule to Windows firewall for WSL2 network #4585
Comments
How to repro. On Windows, listen to some port
On WSL2, try to connect to it: You would not be able to connect until you create appropriate firewall rule |
Nice! New-NetFirewallRule -DisplayName "WSL" -Direction Inbound -InterfaceAlias "vEthernet (WSL)" -Action Allow |
@dansanduleac This allow ping, but how can I access some port on windows , without shutdown the firewall ? |
Thank you so much, I searched for about two hours to make WSL2 launch a graphic Emacs, and this command enabled the use of Emacs GUI, many thanks! |
try add new inbound rule for these ports? |
@eromoe @HQDragon The command I posted should allow you to access anything exposed by Windows from WSL, no matter what port, however bear in mind that any apps you've launched get an automated rule created for them when you first launch them, blocking access from public networks (this is when you get a prompt from Windows Firewall, asking whether the app should be allowed to accept connections from public networks). If you don't explicitly allow, they will be blocked by default, which also blocks connections from WSL. So you might need to find that inbound rule, and change it from block to allow (or just delete it). More info here (linked from this comment on the original issue #4139 (comment)) |
this should be in the docs |
In case this helps anyone: I was trying to setup a new laptop that I just bought and nothing here worked. That's when I realized the Windows machine I just bought had a McAfee Firewall on it (free one year subscription). So all the windows firewall stuff wasn't actually working cause it wasn't the active Firewall (McAfee was) and they have known compatibility issues with WSL/WSL2. Once I uninstalled the McAfee firewall (you could also just disable it), everything here worked except the telnet stuff. For some reason that still didn't work, but I was able to connect to my X servers no problem, which is probably why most of us were here. |
If you are trying to connect to a Mongo installs rules That is 6 hours I won't get back! I hope you are saved that time. |
this is still extremely unreliable, I've
I can't reach the
Does anyone know some reliable trick that I can use to develop web interfaces under WSL2? |
You can hit the IP address that Ubuntu is using if you're using the same machine (ifconfig from WSL2 terminal will give you this address) - is that what you mean? What I'm running into is trying to hit that IP from a wifi connected device like a phone or something. I'm definitely in over my head here, but was hoping changing the -InterfaceAlias to 'vWan' or something would do the trick, but a) I don't know where to find the correct term for that alias, and b) I don't know if that's even how it works - maybe WSL interprets incoming wifi requests through the vEthernet adapter? |
I'm still having this issue as well when trying to debug my application from within the WSL using Intellij's Pycharm |
Thank you so much for that hint! I was about to give up. Setting up the specific IP Range for the "Remote IP Adresses" has done the trick for me. -> #4139 (comment) |
Sometimes I have problems with the WSL network, but this always do the trick: |
I resolved it as this thread: #4139 (comment) |
Thank You! This solved an issue I've been facing for over a month. For some reason after updating to Windows 11, fetching repositories by VSCode (which was started from WSL) was unbearably slow. This solved it! |
Does anyone know how to do this for an outbound rule? I´ve tried just changing the direction to no success |
@marriagav Very naively, I tried this: And it worked for me! This is the only thing that has worked in fact, among tons of others that I've tried 😄 |
I tried all of the above as well as this thread: [https://github.com//issues/4139] to no avail. Windows 21H2 Just trying to use GTK-3 on VSCode with a WSL2 Ubuntu terminal. Using VcXsrv running in background.
I installed xfce4 but that doesnt work too. Upon running this:
Restarted everything several times. |
For my instances, #Requires -RunAsAdministrator
Set-NetFirewallProfile -Profile Private -DisabledInterfaceAliases "vEthernet (WSL)"
Set-NetFirewallProfile -Profile Public -DisabledInterfaceAliases "vEthernet (WSL)" |
win 11 failed:
so after I do |
I tested this. This is work for not only WSL NIC but all Interfaces. |
I was trying to connect to Windows machine from Linux and found that it is blocked by default.
WSL virtual NIC connection belongs to "Public" profile and almost all connections are forbidden.
As workaround, I added following rule explicitly:
Workaround works. But it would be great to have this rule enabled by default.
The text was updated successfully, but these errors were encountered: