Android Integrations
The various Andorid integration features for WG Tunnel.
Remote App Control with Intents
WG Tunnel enables other apps (like Tasker, MacroDroid, etc) to control toggling tunnels and auto-tunneling via intents.
Available actions:
- Vpn on by tunnel name
- Vpn off by tunnel name
- Start auto-tunnel
- Stop auto-tunnel
NOTE: For secure purposes, this feature needs to first be turned on by the user in the app settings. Turning on this feature will generate the key used in the intents to ensure the intent is a valid request. Click on this key to copy it to your clipboard.
Example request to start a tunnel:
am broadcast \
-a com.zaneschepke.wireguardautotunnel.START_TUNNEL \
-n com.zaneschepke.wireguardautotunnel/com.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver \
--es key "<your-key>" --es tunnelName "<tun-name>"
Example request to start auto-tunnel:
am broadcast \
-a com.zaneschepke.wireguardautotunnel.START_AUTO_TUNNEL \
-n com.zaneschepke.wireguardautotunnel/com.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver \
--es key "<your-key>"
List of all possible actions:
com.zaneschepke.wireguardautotunnel.START_TUNNEL
com.zaneschepke.wireguardautotunnel.STOP_TUNNEL
com.zaneschepke.wireguardautotunnel.START_AUTO_TUNNEL
com.zaneschepke.wireguardautotunnel.STOP_AUTO_TUNNEL
Component (important for security):
com.zaneschepke.wireguardautotunnel/com.zaneschepke.wireguardautotunnel.core.broadcast.RemoteControlReceiver
NOTE: If you are using a nightly or prerelease version, first half of the component path (app package section) could be slightly different so check the installed package name to adapt this. This is only for the first half before the
/
.
Extras:
key
: required for all requests and generated by the app when you turn on this feature.tunnelName
: only necessary for start and stop tunnel actions. If not found, the primary or first tunnel will be used.
Example in app:
Last updated 17 Apr 2025, 05:05 -0400 .