You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Connect to Wi2 installed at Starbucks
Make Wireguard connections
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.
The text was updated successfully, but these errors were encountered:
Is it a bug?
I have checked if others have reported this already
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
Failure Logs
Android version
15
Device model
Pixel 7 Pro
Mullvad VPN app version
2024.10-beta2
Additional Information
The text was updated successfully, but these errors were encountered: