GeezerVison is showing github.com — wsl: Hyper-V firewall is not supported wsl: Mirrored networking mode is not supported, falling back to NAT networking · Issue #10495 · microsoft/WSL
wsl: Hyper-V firewall is not supported wsl: Mirrored networking mode is not supported, falling back to NAT networking #10495DescriptionWindows Version
10.0.25931.1000
WSL Version
2.0.0.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.123.1-1
Distro Version
ubuntu 22 and kali linux
Other Software
cmd
Repro Steps
wsl - kali or ubuntu:
error:
wsl: Hyper-V firewall is not supported
wsl: Mirrored networking mode is not supported, falling back to NAT networking
Expected Behavior
wsl - kali or ubuntu:
error:
wsl: Hyper-V firewall is not supported
wsl: Mirrored networking mode is not supported, falling back to NAT networking
but linux will start
Actual Behavior
wsl - kali or ubuntu:
error:
wsl: Hyper-V firewall is not supported
wsl: Mirrored networking mode is not supported, falling back to NAT networking
but linux will start
Diagnostic Logs
No response Reacted by Michiel Lankamp, Heechul So, Mendel Greenberg, Lucas Espinar, Gabriele Castellano, ChanCody and Asad Kamal Activitybenhillis commented on Sep 19, 2023 microsoft-github-policy-service commented on Sep 19, 2023 Hello! Could you please provide more logs to help us better diagnose your issue?
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 scipt will output the path of the log file once done.
Once completed please upload the output files to this Github issue.
Click here for more info on logging
Thank you! Morrigan-Ship commented on Sep 19, 2023 mlankamp commented on Sep 19, 2023 mrdev023 commented on Sep 19, 2023 Morrigan-Ship commented on Sep 19, 2023 i think i know how we can fix it
but i cannot do it because important information
if anyone tested send the result
:
in first remove all linux distro then full remove wsl(dont remove wsl in first)
secend install wsl
install new distro
test with new network config and send result Reacted by Nick Chevsky, Charles Bayley, Dan the security engineer, MaskYuan(SII), Mihai Ene, marceldempers, Caelum Zhu, lo, Skylar, Alvaro and 3 more benhillis commented on Sep 19, 2023 Keith Horton (@keith-horton) - Could we adjust the error message so it's clear that the version of Windows they are running does not support the feature? It's currently a little confusing. Reacted by Michiel Lankamp Morrigan-Ship commented on Sep 19, 2023 Reacted by Nick Chevsky and Cheese sf467 commented on Sep 20, 2023 My win11 is dev, Build 23545 ,and have the same problem oidualc commented on Oct 13, 2023
running 'ip a' in a Linux prompt to see if the IP addresses assigned in the Linux container are the same as the IP addresses assigned to Windows.
Confirmed.
You can use the New-NetFirewallHyperVRule powershell command'let to add a new rule.
My understanding was that using "firewall=true" in .wslconfig and disabling the Windows Firewall altogether, WSL should have picked it up automatically. Not working this way, could you be more specific about what command to run? I tried something like this one with no luck. keith-horton commented on Oct 13, 2023 Hi there.
Setting firewall=true in the .wslconfig file will enable Hyper-V Firewall for that WSL container instance. If the host Windows Firewall is enabled, we will mirror all Windows Firewall rules that are based on IP addresses or port numbers (not user ids or applications). And you can run NetFirewallHyperVRule powershell command'lets to view/add/remove rules for Hyper-V Firewall.
If you have an OS with the necessary updates, these powershell commands should work. Both of these must work for Hyper-V Firewall to be enabled.
get-NetFirewallHyperVVMCreator
this should show something like;
VMCreatorId : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
FriendlyName : WSL
get-NetFirewallHyperVProfile
this should show Public, Private, and Domain profiles like
Name : {40E0AC32-46A5-438A-A0B2-2B479E8F2E90}
Profile : Public
.
.
. isaali93 commented on Oct 27, 2023
Windows Version Last build WSL2
Windows Insider Canary Channel 25951 🪞Mirrored networking support
Windows Insider Dev Channel 23555 ❓
Windows Insider Beta Channel 22621.2338 ❓
Windows Insider Release Preview Channel 22631.2361 🪞Mirrored networking support
Windows Public Release (KB5030310) 22621.2361 🪞Mirrored networking support
Dev and Beta channels should get the support in the next builds.
Hey, you guys have any word on when this is coming to Dev? It's been sometime already lc-guy commented on Nov 1, 2023 Any information on having support for this on windows 10, or is it just not coming to it at all? Reacted by Philipp G., dlonghi, CrisNevares, Jorge Marques, Rodion Alekseenko and kacpersyn keith-horton commented on Nov 1, 2023 Sorry, we have asked. As of today, we do not have plans to take this back to Windows 10. Reacted by Brad M, Jingbei Li, Philipp G., waltz, kanine, Jorge Marques, FromTheMoon, Luke, Sergio Sánchez Vallés, Rodion Alekseenko and 3 more isaali93 commented on Nov 1, 2023 Looks like mirrored networking is enabled on the dev channel as of today's 23580 build. hanxinimm commented on Nov 25, 2023 Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x803b0015 keith-horton commented on Nov 28, 2023 Hi there. If you are hitting a new error code, can you open a new GitHub issue + capturing traces? K2ouMais commented on Dec 12, 2023 Can someone explain, why this doesnt work under Windows 10?
It is a shame, because corporate machines will stay on Windows 10 for a long time and Windows 11 ist still not an option for many corporations.
[experimental]
networkingMode=mirrored
dnsTunneling=true
I have a corporate Laptop without any Admin rights, so I have only this way of getting wsl configured.
I really want to get rid of "wsl-vpnkit" when I am behind a VPN. Reacted by Sergio Sánchez Vallés keith-horton commented on Dec 14, 2023 Sorry, those features are not available on Windows 10. They are only on Windows 11. boan-jfm commented on Jan 18, 2024 Reacted by João Alves and Jorge Marques K2ouMais commented on Jan 18, 2024 It's a shame this is Windows 11 only where almost every company is still using Windows 10. Sometimes I really question some decisions. jtrenaud1s commented on Jan 25, 2024
It's a shame this is Windows 11 only where almost every company is still using Windows 10. Sometimes I really question some decisions.
Same boat. Super annoying. Though I do have local administrator privileges, I still have not found any workaround to the VPN issue. Also stuck on windows 10. Reacted by João Alves and shafo K2ouMais commented on Jan 26, 2024 Reacted by Artyom Matveev martopg commented on Aug 7, 2024 I ran across this issues as I was searching for a fix for this:
wsl: Mirrored networking mode is not supported: Windows version does not have the required features
For anyone else that's seeing that: I was on Win11 23H2 but didn't have the latest updates for it and installing those resolved the issue. Reacted by Keith Horton and Caelum Zhu
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|
