![]() If at any time the VPN goes down, also bring Transmission (and the Telegram bot) down gracefully.If that goes through, run Transmission (and the Telegram bot).If the VPN connection goes through, configure Transmission to run through it.Start OpenVPN at boot (after networking is up).Ideally, I'd be able to do something a bit more like what this post outlines, though I'm not particularly picky about whether all the traffic goes through the VPN or if only the torrent traffic does: bin/sed s/IP_ADDRESS/$4/ /var/lib/transmission/.config/transmission/settings_template.json > /var/lib/transmission/.config/transmission/settings.json I might add that in addition to OpenVPN and Transmission, I also have this Telegram bot that should start after all else is up, so my up.sh file also has one more line at the end and looks like this: #!/bin/sh ![]() ![]() Sudo openvpn -cd /etc/openvpn -config /etc/openvpn/conf.ovpn -script-security 2 -up /etc/openvpn/up.sh I'm able to get everything to run by following the steps here and here - but that only works when running the script ( vpn.sh, as per the two tutorials) manually. I'm trying to set up Transmission with OpenVPN on a headless server running a minimal install of CentOS 6.10, and ideally these would start when I boot the system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |