Skip to content
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

DAITA not working when WireGuard Shadowsocks are enabled. #7160

Open
2 tasks done
outofmeow opened this issue Nov 11, 2024 · 3 comments
Open
2 tasks done

DAITA not working when WireGuard Shadowsocks are enabled. #7160

outofmeow opened this issue Nov 11, 2024 · 3 comments
Labels
bug Linux Issues related to Linux

Comments

@outofmeow
Copy link

Is it a bug?

  • I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

  • I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

If you try to connect with the Mullvad VPN over the Wireguard Shadowsocks obfuscation with DAITA enabled, it is stuck in a loop while connecting to a server.

Expected Behavior

It connects to the Mullvad server.

Steps to Reproduce

  1. Enable DAITA
  2. Enable Wireguard with Shadowsocks

Failure Logs

No response

Operating system version

Linux

Mullvad VPN app version

Broke: 2024.7 (and probably earlier I think it started with 2024.6)

Additional Information

No response

@outofmeow outofmeow added the bug label Nov 11, 2024
@gsture
Copy link

gsture commented Nov 12, 2024

#6864 might be related.

@dlon dlon added the Linux Issues related to Linux label Nov 12, 2024
@dlon
Copy link
Member

dlon commented Nov 12, 2024

Thanks for the report!

Does lowering the MTU to some low value (such as 1280) make any difference? Does it help to connect directly to some relay without using multihop (e.g. by selecting Netherlands as your exit relay)?

@outofmeow
Copy link
Author

outofmeow commented Nov 12, 2024

Hey :3
Lowering the MTU makes it possible to connect and using the direct only option too.

Maybe something related when hopping to the secondary / exit server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Linux Issues related to Linux
Projects
None yet
Development

No branches or pull requests

3 participants