Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Privacy friendly way to turn on Wireguard depend on home/away scenario #1294

Open
iulko opened this issue Mar 18, 2024 · 2 comments
Open

Privacy friendly way to turn on Wireguard depend on home/away scenario #1294

iulko opened this issue Mar 18, 2024 · 2 comments

Comments

@iulko
Copy link

iulko commented Mar 18, 2024

I was looking for a privacy friendly way to check if we are home or away from home so that we know if wireguard (and other things) should be on or off. Tasker integration is a big project but this simplify it to some extent and is what most people need.

The only information we propably get about network you connect is IP you get assigned, mask, gateway and DNS.
Because ssid/wifi name checking needs location service its a no no for most people.

Could we have a way to for example to treat a Wireguard tunel as "turned off" when DNS IP is specific IP, or IP you got assigned is a specific IP? This would not turn off Wireguard tunel like if you do it yourself, it would just make the tunel act as "turned off" if your system DNS IP is a specific IP.

Wireguard tunel "Test" is turned on -> Is ON in every network -> when a network have system DNS IP 192.168.5.12 than wireguard gets disabled but not turned off, its just skipped.

Any questions or doubts please let me know

@ignoramous
Copy link
Collaborator

ignoramous commented Mar 18, 2024

@ignoramous
Copy link
Collaborator

A user writes,

The official Wireguard app uses these intents which creates a custom permission. Then in this file, the intents are handled. Where needed, the tunnel name is specified as a parameter. I couldn't find anywhere that allows Tasker to detect the function named WireGuardSetTunnel that it uses to control WG, but as far as I can tell, that function is simply a wrapper for an intent broadcast. Tasker can directly perform such broadcasts as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants