-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
quantum resistant tunnel may cause wireguard connections to not work #7231
Comments
Hi! You mention that you sit on a heavily filtered corporate internet which I would like to dig a bit deeper into. When you manage to connect successfully, which feature indicators show up on the main app screen? Also, does it work with PQ if you also enable some kind of obfuscation? If you have the time and energy, please try with both Shadowsocks and UDP2TCP. The latter is likely to perform pretty badly, but it could be an interesting datapoint 😊 |
|
That's amazing, thanks a lot! I guess the last thing to look into are the daemon logs then 😊 Would you mind pasting them here? If you extract them by navigating to |
You are welcome! I have sent the logs to the support team. |
FWIW the suggested workaround here also solves my connection issues (identical to OP's): app fails to connect on default settings, turning off quantum resistant tunnels solves the problem. |
Just wanted to add that I'm having difficulty with 2024.8 shutting down despite lockdown mode & killswitch both being ON. I'm also using quantum-resistant. Mullvad shuts itself down randomly after about a half hour and exposes the machine to open internet traffic. And this happens invariably when the machine goes to sleep but wakes back up. On Linux Mint OS. Very scary. Hope disabling quantum-resistant will solve the problem. Otherwise, relying on Mullvad VPN will be itself a security risk. |
If that's the case, please assist us in finding the root cause of this by forwarding logs to our support team or opening up a new GitHub issue where we can have a more focused discussion (since it goes beyond the scope of this issue). We take unwanted traffic leaks very seriously, and they always have the highest priority from us. You can forward anonymized logs from within the app by going to Stay safe 💛 |
Is it a bug?
I have checked if others have reported this already
Current Behavior
I had quantum tunneling on "Automatic", and everything else on default.
The app will try to connect wireguard, the connection is established successfully. However, there is no actual internet access. The app will eventually time out the VPN connection and try connecting again. The situation repeats itself.
Expected Behavior
When trying to connect via wireguard and an issue arises as a result of quantum tunneling, the "automatic" option in quantum tunneling app should act accordingly.
Switching quantum tunneling to "off" fixes the issue
Steps to Reproduce
This issue is likely difficult to reproduce because it only occurs on a heavily filtered corporate internet. Nonetheless, my main concern is improving the "automatic" functionality for the "quantum tunneling" feature.
Anyways, to reproduce the issue,
1- Set quantum tunneling to "Automatic"
2- Try to initiate a VPN connection with wireguard
Failure Logs
No response
Operating system version
Linux mint 22
Mullvad VPN app version
2024.7 (version maybe unrelated)
Additional Information
I can confirm that this fixed my wireguard connection issue on 2 systems.
The text was updated successfully, but these errors were encountered: