[Feature request] Add private/multiple wireguard peer(s)

[cegfault]

Issue report

Operating system: Android App version: (latest - feature request)

Issue description

I would like to be able to add a custom/private wireguard Peer to the android app (for example, for access to a certain corporate or private wireguard service). Currently, it is possible to create a wireguard configuration file and manually add a second Peer section, and then use the Wireguard app on Android. This would route all traffic through Mullvad's endpoint except the private Peer access.

However, this is not ideal. Every time I want to switch to another endpoint I would need to generate a new wireguard configuration file, manually add the [Peer] section, and then add it into the Wireguard app. Having a native way to handle this would be ideal.

For reference, my work has development resources behind a wireguard vpn. Android doesn't really allow for Wireguard and Mullvad to run simultaneously.

I think it would be quite beneficial to have a section where I could add a [Peer] endpoint with a specific AllowedIPs (say, 10.x.y.z/24). This way, the app could change wireguard endpoints seamlessly without requiring significant manual attention on my part.

[cegfault]

P.S. Split Tunneling is not sufficient, as it only allows a specific app to bypass the VPN. What's needed is a second endpoint - another [Peer] section. Again, this is operational with manually editing wireguard configuration files, but requires significant (manual) effort when changing to a new Mullvad server/endpoint.

[faern]

Thanks for the suggestion. This is a feature we are tracking internally on some kind of wish list. It's currently not a high priority, but something we agree would be cool to have at some point.

[alexl4321]

second that. would be great. its a huge headache to manage multiple wireguard networks in a corporate context. this would solve many problems.

[Dzjed]

This would be a great feature. I can't use the app and have to use wireguard config files right now for this use case.