Replies: 2 comments 3 replies
-
This would be nice to have. As a workaround (on Linux), I wrote a bash wrapper script for Transmission that refuses to start it if my VPN is not active. I wrote another bash script that runs as a daemon in the background and checks the VPN status every five seconds and kills Transmission if the VPN is not active. When it does so, it keeps running and restarts Transmission when the VPN becomes active again. Scripts available (as is) upon request. |
Beta Was this translation helpful? Give feedback.
-
This can be configured in most VPN clients as a kill switch that automatically disables your connectivity if the VPN connection fails. Some providers, like NordVPN, provide granular application-level kill switches so you can only enable it for Transmission, while others are system-level. |
Beta Was this translation helpful? Give feedback.
-
Can you add a settings option that requires a VPN connection before proceeding with transmission activity?
Can you also halt activity if the VPN connection is accidentally turned off?
Are you able to automatically run the VPN with a default connection?
Since a VPN is so important, it would be a nice option to require its use based on my settings preference.
Thanks for considering the idea.
Beta Was this translation helpful? Give feedback.
All reactions