Open TommyTran732 opened 5 months ago
Thanks for reporting this issue. This is probably a duplicate of/related to #5213. Admittedly we have not spent a great amount of time testing compatibility with UTM virtualization.
For what it's worth, I had a similar problem (discussed in https://github.com/mullvad/mullvadvpn-app/issues/5213#issuecomment-1899007933) and now have the guest OS (Windows 11) working on the QEMU backend regardless of whether Local Network Sharing
is enabled or not.
Is it a bug?
I have checked if others have reported this already
Current Behavior
Mullvad blocks UTM's VMs in Emulated VPN unless we allow local network connection.
Expected Behavior
Mullvad should only block connections to the actual LAN and not the Emulated VPN running inside of the machine.
Steps to Reproduce
Failure Logs
Operating system version
macOS 14.2.1
Mullvad VPN app version
2023.6
Additional Information
I don't know how macOS networking under the hood, but I have tested this with IVPN, and their client does work for this scenario. VMs with Emulated VLAN can connect to the internet even access to the real LAN is not allowed.
There is probably a way to differentiate between the Emulated VLANs and the actual LAN/WLAN. I am not sure what they actually do though, I haven't looked at the code yet.