[EMAIL PROTECTED] wrote:
> Hi Frank,
>
> Thanks for sharing this with me as it is very useful and will allow me to
> possibly remove the OpenVPN part from the design that we are considering
> since Bacula seems to be able to take care of this matter for us as a
> built in feature.
>
> I guess that I still have the major question of being able to traverse
> firewalls and routers since as you have mentioned that the Bacula server
> initiates the connections to the clients and the client software does not
> initiate any connection to the server although I think that would be a
> nice feature as well.
If you're traversing firewalls, it sounds like you need to establish 1
VPN per firewall, then use routing to route the Bacula services through
the VPN.
Bacula's TLS isn't going to do that for you. Is there some reason why
you can't just establish a persistent VPN between the Bacula server and
the firewall and run the jobs across it?
--
Bill Moran
When I point out limitations of one technique as a motivation for another, I
do so in the context of specific problems; for different problems or in other
contexts, the first technique may indeed be the better choice. Useful
software has been constructed using all of the techniques presented here.
Bjarne Stroustrup, _The_C++_Programming_Language_
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
