diff options
| author | Sebastian Holmin <sebastian.holmin@mullvad.net> | 2025-03-27 11:30:09 +0100 |
|---|---|---|
| committer | Sebastian Holmin <sebastian.holmin@mullvad.net> | 2025-03-27 11:44:24 +0100 |
| commit | 9cfbe3dd709d69b6832b55600500ff9d2f9fc84c (patch) | |
| tree | 9c4fcd02230c60a8074e4f0ab585f4f53aa85568 | |
| parent | ebd93e0f9d92640362a7a89c72b79eba26277a79 (diff) | |
| download | mullvadvpn-9cfbe3dd709d69b6832b55600500ff9d2f9fc84c.tar.xz mullvadvpn-9cfbe3dd709d69b6832b55600500ff9d2f9fc84c.zip | |
Add note on `NetFirewallHyperVProfile` in known issues
| -rw-r--r-- | docs/known-issues.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/known-issues.md b/docs/known-issues.md index 73c8a6e2bc..1b0cc2b94e 100644 --- a/docs/known-issues.md +++ b/docs/known-issues.md @@ -190,7 +190,10 @@ exempted since the routing table will ensure that traffic is tunneled in that ca (see details below). There are certain limitations to this mitigation. First, the Hyper-V firewall is only available on -*Windows 11 version 22H2 and above*, so it has no effect on earlier versions of Windows. +_Windows 11 version 22H2 and above_, so it has no effect on earlier versions of Windows. The +Hyper-V firewall profile must not be disabled, which can be inspected using the +`Get-NetFirewallHyperVProfile` PowerShell command. + Additionally, LAN traffic will never be blocked while connected, regardless of whether "Local network sharing" is enabled. Moreover, DNS leaks are more likely to occur. |