Skip to content

[Feature request] Add per-app routing controls for remote VPN connections #723

Description

@sin-34

Is your feature request related to a problem? Please describe.

TrackerControl now supports remote VPN routing through Mullvad, IVPN and custom WireGuard configurations. However, the remote VPN option appears to apply globally to every app included in TrackerControl.

TrackerControl already has an “Exclude from VPN” option for individual apps, but this is not equivalent to remote-VPN split tunnelling: excluding an app also removes it from TrackerControl’s local monitoring and tracker blocking.

I would like to keep all my usual apps protected by TrackerControl while allowing only selected apps to use the configured remote VPN tunnel.

Describe the solution you'd like

Please add a separate per-app routing control inside the VPN section, independent of “Exclude from VPN.”

Possible modes could be:

  • Route all monitored apps through the remote VPN.
  • Route only selected apps through the remote VPN.
  • Route all monitored apps except selected apps through the remote VPN.

Apps that are not routed through the remote VPN should continue to be monitored and filtered locally by TrackerControl, but their permitted traffic should use the device’s normal Wi-Fi or mobile-data connection.

The imported WireGuard profile’s AllowedIPs should still be respected for apps selected to use the tunnel.

Example use case

I use a custom WireGuard profile to reach services on my private homeserver.

I would like:

  • Nextcloud, Memories and selected file-management apps to use the WireGuard tunnel.
  • Browsers and other apps to remain protected by TrackerControl while using their normal Internet connection.
  • Apps outside the selected list to have no access to the remote WireGuard route.

This would also be useful with full-tunnel Mullvad, IVPN or custom WireGuard profiles when users want only certain apps to use the remote VPN exit address.

Alternatives considered

  • Using WireGuard "AllowedIPs" provides destination-based routing, but not app-based routing.
  • Using “Exclude from VPN” bypasses the remote tunnel, but also bypasses TrackerControl’s local filtering.
  • Running TrackerControl alongside another VPN client is not possible because Android permits only one active VPN service.

Additional context

This request is specifically about separating two independent choices:

  1. Whether an app is monitored and filtered by TrackerControl.
  2. Whether its allowed traffic is forwarded through the configured remote VPN.

A configurable fail-open or fail-closed option for selected apps when the remote tunnel is unavailable could also be useful, although that could be implemented separately.


Web that was a mouthful! Thank you devs for your hard work, I've been using this app for years and I'm excited to see an VPN option added so I hope you will consider this feature! It would be a great enhancement!!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions