> > > The only way to prevent this behavior as I see it is to add static routes
> > > on both internal network client and DIR/SD server to route all traffic
> > > to/from external interface to internal one transparently for bacula
> > > services. For this to work I would also need to enable routing on both
> > > machines and reconfigure firewall on DIR/SD server. Not an elegant
> > > solution by any means...
> >
> > The Director tells the FD the hostname of the SD. You put the hostname
> > of the SD into the hosts file of the computer the FD is running on. When
> > the client computer resolves the hostname of the SD it will check the
> > hosts file first to see which address to connect to.
> 
> Now I got it ;-). This may work if I edit hosts files on all of my dual-NIC 
> clients as well as on bacula server by substituting external IP address with 
> internal one for machines' own hostnames. This however will screw up hosts 
> resolution for all network applications and no doubt will have implications. 
> For one, mailing system will fail to work since it uses institutional mail 
> gateway on external network which is set up with strict security and will 
> hence reject messages from hostnames not registered in our DNS. There may be 
> other problems as well (OSCAR is rather picky about host name resolution). It 
> is most possible to work around these problems but I'd rather stick with the 
> static cross-routing for now. Sure, it will consume some CPU cycles to route 
> all traffic between two interfaces but at least it is as transparent as 
> possible solution.
> 
> Thanks for the advice however and for being persistent with it! I admit my 
> brains have started to fail after two weeks of struggle with bacula ;-). If 
> static routing won't work as expected I may still give your suggestion a try

No problem. But do note you only need to set up the hosts for the hostname
of the SD, you shouldn't have to mess with any other hosts at all if
they are already working. I've had to set mine up this way because my
backup server has three networks it is a member of. To make it easy on
myself, I call the SD "backup3" a name that will does not resolve in DNS
for any server and is not used for any other purpose. Then on the client
servers I only need one line added to the hosts:
172.30.0.253    backup3
just changing the address depending on what network the client is on. 
-- 
Kenny Dail <[EMAIL PROTECTED]>


-------------------------------------------------------------------------
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

Reply via email to