TCB13 , 8 months ago (edited 8 months ago)

You don’t need to switch to another client. Apparently Transmission can be set to bind to your VPN IP by editing settings.json:

bind-address-ipv4: String (default = “0.0.0.0”) Where to listen for peer connections. When no valid IPv4 address is provided, Transmission will bind to “0.0.0.0”.

bind-address-ipv6: String (default = “::”) Where to listen for peer connections. When no valid IPv6 address is provided, Transmission will try to bind to your default global IPv6 address. If that didn’t work, then Transmission will bind to “::”.

If you set those with your VPN IP and the VPN is down then Transmission won’t be able to communicate with any peers.

---

Another option, is to use systemd to restrict Transmission’s networking to your VPN IP. You can make an override of the default transmission daemon unit by using the following command:

<span style="color:#323232;">systemctl edit transmission-daemon.service
</span>

Then type what you need to override:

<span style="color:#323232;">[Service]
</span><span style="color:#323232;">IPAddressDeny=any
</span><span style="color:#323232;">IPAddressAllow=10.0.0.1 # --> your VPN IP here
</span>

Another systemd option, might be to restrict it to a single network interface:

<span style="color:#323232;">[Service]
</span><span style="color:#323232;">RestrictNetworkInterfaces=wg0 # --> your VPN interface
</span>

Save the file and run systemctl daemon-reload followed by systemctl restart transmission-daemon.service and it should be applied.

This will be safer than just doing bind-address-ipv4 and bind-address-ipv6.

• ctrl.blog/…/systemd-application-firewall.html
• freedesktop.org/…/systemd.resource-control.html#N…
• freedesktop.org/…/systemd.resource-control.html#R…