Martin Simmons wrote: >> The only practical way I can see to break this problem is to reverse the >> direction of the connection so that the director tells the storage daemon to >> contact the file daemon and not the other way around. This would work >> because the remote client machines have a FQDN and are thus easier to reach. >> > Bacula cannot connect in that direction, but you can do it using stunnel, ssh > or a VPN to set up a tunnel from the SD to the FD and then run the FD to SD > communication inside the tunnel. > > Now that's an interesting solution, Martin! It would solve two problems at once; the first being the connection problem and the second being the security problem. I had temporarily put the security issue aside but it made me uncomfortable to think all my sensitive files would be visibly leaking through what is effectively a back door.
I still think I'll have to go for the static IP address solution though. I've been having problems recently with my ISP changing my router's ip address rather *too* dynamically (sometimes it changes every five minutes) and that would play havoc with a stunnel or ssh connection. I know it plays havoc already with any voip conversations in progress! David - ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
