You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever you add javaw.exe to split tunneling, you'd expect for javaw.exe to bypass mullvad, instead of blocks all connections from the process, even when windows firewall is disabled, giving a permissiondenied exception.
I know this has been reported in the past, but I am reporting again because it hasn't been fixed, I saw that the earliest occurrence of this reported had a "wont fix" label, which is incorrect, the issue must be fixed. No other VPNs have this problem.
The text was updated successfully, but these errors were encountered:
The java runtime initializes and handles socket in a very ugly non-standard way. This is currently incompatible with our split tunneling kernel driver. It might be possible, but would be pretty ugly to have the kernel driver accept and work around the hack that Java is doing. They basically only use IPv6 sockets, even for IPv4 connections.
This might be fixed in the future. But it's currently not a very high priority, sorry.
Issue report
Operating system: Windows 11
App version: 2023.4
Issue description
Whenever you add javaw.exe to split tunneling, you'd expect for javaw.exe to bypass mullvad, instead of blocks all connections from the process, even when windows firewall is disabled, giving a permissiondenied exception.
I know this has been reported in the past, but I am reporting again because it hasn't been fixed, I saw that the earliest occurrence of this reported had a "wont fix" label, which is incorrect, the issue must be fixed. No other VPNs have this problem.
The text was updated successfully, but these errors were encountered: