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

Automatic mode of obfuscation does not work properly on certain networks #7738

Open
2 tasks done
mullbird opened this issue Mar 1, 2025 · 1 comment
Open
2 tasks done
Labels

Comments

@mullbird
Copy link

mullbird commented Mar 1, 2025

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

In Japan, there is a membership-based public wireless LAN service called Wi2 (AS111360).

This wireless LAN hotspot uses a special communication control not often seen elsewhere to interfere with the use of Wireguard. It appears to successfully connect to the Wireguard tunnel, but it is not possible to upload within the tunnel. Downloading and pinging can be performed within the tunnel. This inexplicable communication control is taking place regardless of the Wireguard port number.

Expected Behavior

This communication control can be circumvented by using UDP-over-TCP.

However, if the obfuscation setting is set to automatic in the Mullvad app, the connection is made without obfuscation, even though UDP-over-TCP should be enabled. As a result, the user must manually enable UDP-over-TCP.

Is it possible to improve the Mullvad app to detect the communication control and enable UDP-over-TCP automatically? A possible approach would be to connect once, test the TCP upload, and if the upload fails, enable UDP-over-TCP and reconnect.

Steps to Reproduce

  1. Connect to Wi2 installed at Starbucks
  2. Make Wireguard connections
  3. Perform an Ookla speed test

Failure Logs

Android version

15

Device model

Pixel 7 Pro

Mullvad VPN app version

2024.10-beta2

Additional Information

  • This problem may not apply to all Wi2 access points, but only to Wi2 installed at Starbucks.
  • This problem may apply not only to Wireguard, but also to UDP OpenVPN. This problem does not affect TCP OpenVPN.
@mullbird mullbird added the bug label Mar 1, 2025
@mullbird
Copy link
Author

mullbird commented Mar 1, 2025

Twitter posts that may have something to do with this issue

スタバのKDDI(Wi2)系のWi-Fi、VPN接続した後にTCP/UDP 3389な通信は流れるようになったけど、TCP 80/443な通信が流れないのマジで謎。
MTU値の問題かと思ったけど違うようで分けらからん。。。。
https://x.com/harkas_jp/status/1330381819125043207

おっと。スタバはOpenVPNのUDPはブロックしているんですね💦
https://x.com/__snow_rabbit__/status/1377093266659676161

そもそも社内ネットワークに入るためのVPNがスタバの野良WiFiだと通らない気がするけど、通るのかな
openvpnとwireguardがスタバの野良WiFi使えないのは確認した
https://x.com/4TZLaxhuOzKxB5/status/1805491885860950337

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

No branches or pull requests

1 participant