Thanks. I'm aware of this possibility however there's only 1 remote machine in each remote network. This makes setting up OpenVPN for each of those a hassle. It feels like using a shotgun to kill a fly. It also requires to do extra firewalling while with SSH only the needed ports are exposed to the client.
Op za 12 jan. 2019 om 13:41 schreef Heitor Faria <hei...@bacula.com.br>: > *sorry to no answer in line, just adding to the Adam answer. => > http://bacula.us/openvpn-bacula-configuration/ > > Sent from TypeApp <http://www.typeapp.com/r?b=14249> > On Jan 11, 2019, at 7:37 PM, Adam Nielsen <a.niel...@shikadi.net> wrote: >> >> I have a client that's remote. The connectivity to the remote client is >>> established through an SSH script. >>> In general the SSH connection is up or re-established when a job runs >>> through Run Before Job in a JobDefs piece. >>> This works properly. >>> >> >> Just curious - any reason why you're using SSH rather than something >> like OpenVPN? OpenVPN will automatically connect as needed so it's >> much easier to manage in scripted environments, so just wondering what >> makes SSH the preferred option in this case. >> >> Cheers, >> Adam. >> >> >> ------------------------------ >> >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> >>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
