Support Socks5 proxy

[johnassel]

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

When using the Mullvad App on Android with local network sharing enabled I am no longer able to use the Mullvad SOCKS5 proxies like de-dus-wg-socks5-001.relays.mullvad.net through e.g. FoxyProxy in Firefox mobile.
When I disable local network sharing, the proxies are reachable again.
I suspect this is caused by treating 10.0.0.0/8 (where the proxy IPs are located) as an internal IP.

Expected Behavior

Proxies are reachable when local network sharing is enabled.

Steps to Reproduce

1. enable local network sharing
2. try to use Mullvad proxies -> does not work
3. disable local network sharing
4. try to use Mullvad proxies -> works

Failure Logs

Android version

LineageOS 22.2/Android 15

Device model

Fairphone 5

Mullvad VPN app version

2025.4-beta1

Additional Information

No response

[Pururun]

Hi @johnassel

Thanks for the report!

As you have noticed the reason for this behaviour is that if you turn on local network sharing the app will tell the android system to route all local traffic outside the tunnel.

I guess a possible solution would be to not include Socks5 proxies IPs in the list of local IPs, but that might just break things for other users.

[johnassel]

Hi @Pururun

How is this handled with the desktop version? Because there the Mullvad proxies are usable.

[Pururun]

Hi @Pururun

How is this handled with the desktop version? Because there the Mullvad proxies are usable.

On desktop we can be more flexible so that only local network address that are actually used/routed by the local network are routed outside the tunnel. Unfortunately we don't have this information on android so we have to be more blunt.

But we should add some way to solve this since this is a feature we should support fully.

[johnassel]

Not sure if it was the case before but at least the proxy of the currently connected VPN server (10.64.0.1) is reachable.
10.124.0.0/24 for having other remote proxies as exit is still not accessible.
Local network sharing is still enabled.
Currently I'm on 2025.8-beta1.

[Pururun]

@johnassel Hi, sorry for the slow response, I am not aware of anytchanges we have done to the app so it is a bit weird if you have experienced any change in behavior.

[johnassel]

I think previously I didn't test with the proxy on the connected VPN-Server but only with proxies on other remote VPN-Servers.

[Pururun]

I think previously I didn't test with the proxy on the connected VPN-Server but only with proxies on other remote VPN-Servers.

Ok then I understand. :)

[Rawa]

Changing to feature requests as this is not a bug in its current implementation, it is intended. However, I do see the value of users being able to use socks5 proxy with our android app. Moving over to discussions.