diff options
| author | Sebastian Holmin <sebastian.holmin@mullvad.net> | 2025-03-27 11:32:32 +0100 |
|---|---|---|
| committer | Sebastian Holmin <sebastian.holmin@mullvad.net> | 2025-03-27 11:44:24 +0100 |
| commit | 758ac6109af45af60cb4ea6ed90d752e95f7e403 (patch) | |
| tree | 00d3fb6b51acaa3e5a58a06748d72c0ab453419a | |
| parent | 9cfbe3dd709d69b6832b55600500ff9d2f9fc84c (diff) | |
| download | mullvadvpn-758ac6109af45af60cb4ea6ed90d752e95f7e403.tar.xz mullvadvpn-758ac6109af45af60cb4ea6ed90d752e95f7e403.zip | |
Move WSL setting note to WSL subsection
| -rw-r--r-- | docs/known-issues.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docs/known-issues.md b/docs/known-issues.md index 1b0cc2b94e..40d1e34c63 100644 --- a/docs/known-issues.md +++ b/docs/known-issues.md @@ -197,11 +197,10 @@ Hyper-V firewall profile must not be disabled, which can be inspected using the 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. -Your [WSL config] needs to enable the `firewall` setting for the Hyper-V firewall to be enabled. -It is enabled by default. - #### Linux under WSL2 +For the Hyper-V firewall to function, your [WSL config] must not disable the `firewall` setting. + Network traffic from a Linux guest running under WSL2 always goes out the default route of the host machine without being inspected by the normal layers of WFP (the firewall on the Windows host that Mullvad use to prevent leaks). This means that if there is a VPN tunnel |