Open ghost opened 1 year ago
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.
Just came to share my support for this feature request, would love it if compatibility for java applications would be implemented.
Would like to see this as well. Is there any work started on this that we could look at helping out with?
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.