Re: [Bacula-users] Running a script each time a client is addressed

I prefer not editing supplied scripts as they'd have to be adapted with updates. The second suggesstion sounds like a great idea :) I'll look into it. Op ma 14 jan. 2019 om 13:40 schreef Martin Simmons : > Here are two possible solutions: > > * Make the tunnel at startup (e.g. in the script that

Re: [Bacula-users] Running a script each time a client is addressed

Here are two possible solutions: * Make the tunnel at startup (e.g. in the script that starts bacula-dir). * Use something like inetd to make an ssh connection on-demand (e.g. like https://capocasa.net/on-demand-ssh-port-forwarding-with-inetd). __Martin > On Fri, 11 Jan 2019 20:55:04

Re: [Bacula-users] Running a script each time a client is addressed

> 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

Re: [Bacula-users] Running a script each time a client is addressed

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

Re: [Bacula-users] Running a script each time a client is addressed

*sorry to no answer in line, just adding to the Adam answer. => http://bacula.us/openvpn-bacula-configuration/ ⁣Sent from TypeApp ​ On Jan 11, 2019, 7:37 PM, at 7:37 PM, Adam Nielsen wrote: >> I have a client that's remote. The connectivity to the remote client >is >> established through an

Re: [Bacula-users] Running a script each time a client is addressed

> 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

[Bacula-users] Running a script each time a client is addressed

Hi, What I'm trying to do feels obvious but I can't find what I'm looking for. 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