Sadly the inital setup did not work as smooth as I assumed, so I wrote my setup procedure up. I did some searching around and found dperson’s docker images which nicely provide all needed functionality.

What you wouldn’t want is the container to automatically use my “normal” network connection - this would use my public IP address and throught that might leak my identity. This setup should be fail-secure: if the VPN tunnel gets disconnected, the bittorrent download container will loose network connectivity. To improve reusability I will use docker images for those. the software that should run through/behind the VPN.You can replace that with your company or tor proxy for the other use cases. a Private Internet Access VPN tunnel – this hides (or should hide) my identity.To achieve a secure setup I want to combine the following: The same requirements arise for different use-cases, e.g., when downloading bittorrent files or forcing traffic through the tor network if whistle-blowing. I do not want for traffic to ever leave that VPN as that would look like as if I’d be performing cyber attacks from my private home IP address. Sometimes I want to work on client assignments (penetration-tests) from home, if I do that I am using my company VPN so that all traffic is routed thorugh their public IP address (which is white-listed by the client).

Torrent tor network